Easy to use the SQLServer Browser

SQLServerBrowser runs on the server as a Windows service. SQLServerBrowser listens for incoming requests to SQL Server resources and provides information about SQL Server instances installed on computers. SQLServerBrowser can be used to perform the following three operations: browse the available server to connect to the correct server instance connection

SQL Server Browser runs on the Server as a Windows service. The SQL Server Browser listens for incoming requests to SQL Server resources and provides information about the SQL Server instance installed on the computer. SQL Server Browser can be used to perform the following three operations: browse the available Server to connect to the correct Server instance connection

　　SQL Server BrowserRun on the server as a Windows service. The SQL Server Browser listens for incoming requests to SQL Server resources and provides information about the SQL Server instance installed on the computer. SQL Server Browser can be used to perform the following three operations:

1. Browse available servers
2. Connect to the correct server instance
3. Connect to the dedicated administrator connection (DAC) Endpoint

The SQL Server Browser Service (sqlbrowser) provides the Instance name and version number for each instance of the database engine. SQL Server Browser is installed with SQL Server 2005 to help earlier versions of SQL Server running on the computer (starting from SQL Server 7.0.

By default, the SQL Server Browser Service is not enabled for SQL Server Express. SQL Server Browser canUseThe peripheral application configurator tool performs initial configuration andUseManage the SQL Server Configuration Manager.

　　Background

Before SQL Server 2000, only one SQL Server instance can be installed on one computer. SQL Server listens for incoming requests from port 1433. This port is allocated to SQL Server by the official Internet number distribution organization (IANA. Only one SQL Server instance canUseTherefore, when SQL Server 2000 introduces support for multiple SQL Server instances, it develops the SQL Server Resolution Protocol (SSRP) for listening to port 1434. The name and instance of the installed instance used by this listener serviceUseTo respond to client requests. To address SSRP System Restrictions, SQL Server 2005 provides the SQL Server Browser service to replace SSRP.

　　SQL ServerBrowserWorking Principle

After an SQL Server instance is started, if TCP/IP or VIA is enabled for SQL Server, the Server will be allocated a TCP/IP Port. If the named pipe protocol is enabled, SQL Server listens to a specific named pipe. The specified instance willUseThis port or pipeline exchanges data with client applications. During the installation process, port 1433 and MPs queue \ SQL \ query are allocated to the default instance, but the server administrator canUseModify the SQL Server Configuration Manager. Only one SQL Server instance canUseTherefore, different port numbers and MPs queue names are allocated to the named instance, including SQL Server Express. By default, the named instance is configuredUseDynamic port. Therefore, an available port is allocated when SQL Server is started. You can assign specific ports to the SQL Server instance. During connection, the client can specify the required port. However, if the port is dynamically allocated, the port number may be changed when SQL Server is restarted. Therefore, the correct port number is unknown to the client.

After the SQL Server Browser is startedUseUDP port 1434. The SQL Server Browser will read the registry, identify all SQL Server instances on the computer, and indicate themUse. When a Server has two or more NICs, SQL Server Browser returns all enabled ports for SQL Server. SQL Server 2005 and SQL Server Browser support ipv6 and ipv4.

If the SQL Server 2000 and SQL Server 2005 clients request SQL Server resourcesUseThe port 1434 sends a UDP message to the server. SQL Server Browser responds with the requested instance's TCP/IP Port or named pipe. Then, the network library in the client application willUseThe port or named pipe of the required instance sends a request to the server to complete the connection.

　　UseSQL ServerBrowser

When the SQL Server Browser Service is not running, if you provide the correct port number or named pipe, you can still connect to SQL Server. For example, if the default instance of SQL Server runs on port 1433, you canUseTCP/IP connects to this default instance.

Unable to perform the following connection:

When not all parameters (such as TCP/IP ports or named pipes) are specified completely, the component tries to connect to the named instance.

Component that generates or transmits information about the server or instance to be reconnected.

Connect to the named instance without a port number or MPs queue. This includes the data image of the named instance and the clustered named instance.

To the named instance or default instance (if notUseTCP/IP port 1434.

OLAP Redirection Program service.

Enumerate the servers in SQL Server Management Studio, Enterprise Manager, or query analyzer.

In the client server solutionUseSQL Server (for example, if an application accesses SQL Server over the network), you must assign a specific port number to each instance to stop or disable the SQL Server Browser Service, and write client application code to alwaysUseThis port number. This method has the following problems:

The client application code must be updated and maintained to ensure that it is connected to the correct port.

If other services or applications on the server canUseThe port you select for each instance will make the SQL Server instance unavailable.

　　Parallel installation of SQL Server 2000

In SQL Server 2000, the SQL Server service identifies the Server connection endpoint. In SQL Server 2005, this function is implemented through the SQL Server Browser Service. If you install SQL Server on a computer that is still running SQL Server 2000 or MSDE, you must upgrade them to SP3 or later. Versions earlier than SP3 cannot correctly share port 1434, and the SQL Server instance may not be used to request client applications. Although the SQL Server Browser Service can be started before SQL Server 2000 or MSDE by changing the startup sequence, we recommend that you update all older versions of SQL Server to the latest Service Pack.

When an SQL Server 2000 instance is installed on a computer, if the SQL Server Browser is not running, the SQL Server 2000 listener service is started. If SQL Server Browser is started after the listener service is started, it takes five seconds to wait for SQL Server 2000 to discard port 1434. If the port is not abandoned, SQL Server Browser cannot be started. For SQL Server 2000 versions earlier than SP3, to solve this problem, you need to stop SQL Server 2000, start SQL Server Browser, and then restart SQL Server 2000. SQL Server 2000 listener service will continue to tryUsePort 1434 is enabled. Therefore, upgrade the SQL Server 2000 instance to SP3 as soon as possible.

SQL Server 7.0 does not conflict with SQL Server Browser.

　　Install, uninstall, and run through command lines

By default, the SQL Server Browser Program is installed in C: \ Program Files \ Microsoft SQL Server \ 90 \ Shared \ sqlbrowser.exe. If SQL Server 2000 is installed on a computer but has not been upgraded to SP 3 and SQL Server 2000 instances are not upgraded, stop SQL Server 2005 during installation of SQL Server 2000. If SQL Server 2000 is running, SQL Server Browser cannot be started orUsePort 1434, and the installation may fail due to a lack of connection.

The SQL Server Browser Service is uninstalled after the last instance of SQL Server 2005 is deleted. The SQL Server 2000 instance restores its original behavior.

YesUse-C switch: start SQL Server Browser from the command line to troubleshoot the fault.