SQL Server Protocols Highlights
Choosing a Network Protocol
To connect to SQL Server Database Engine, you must have a network protocol enabled. Get an introduction to these network protocols and a background on these options.
Network Protocols and TDS Endpoints
TDS is a protocol that enables clients to carry a database-specific conversation with SQL Server. All our data providersSNAC, SqlClient, and JDBCuse TDS. Get an overview of this protocol and see usage examples.
Configuring Server Network Protocols and Net-Libraries
Get an overview of configuring your server and a description of the protocols for various installation configurations.
Using SQL Server Browser
SQL Server Browser runs as a Windows service on the server. SQL Server Browser listens for incoming requests for SQL Server resources and provides information about SQL Server instances that are installed on the computer. Learn more here.
How to: Start and Stop the SQL Server Browser Service
Learn how to start and stop the SQL Server Browser service.
Default Client Connection Behavior
After installing SQL Server Native Clienton a client computer, the client is immediately ready to connect to an instance of the database engine. In most cases, a SQL Server client does not need any special configuration to connect to an instance of the Database Engine.
Geo-Replication Performance Gains
Extensive replication performance testing compared SQL Server 2005 running on Windows Server 2003 against SQL Server 2008 running on Windows Server 2008. Both operating environments replicated data between a server located in Tukwila, Washington, and another located in Blueridge, Virginia—a distance of approximately 3,000 miles. The results show that SQL Server 2008 running on Windows Server 2008 yielded up to 100 times faster performance without requiring any expensive wide area network (WAN) acceleration hardware.