SQL Server Browser para SQL Server 2012 11.0.2100.60

SQL Server Browser is a Windows service that facilitates the discovery of SQL Server instances on a network. It enables clients to connect to the appropriate SQL Server instance by resolving the instance name correctly.

If you have multiple instances of SQL Server running on the same machine, each instance should be assigned a unique TCP/IP port. In this case, you will need SQL Server Browser to connect to the correct instance. Otherwise, you can disable SQL Server Browser to reduce your system's attack surface.

SQL Server Browser listens on UDP port 1434 for requests to connect to a named instance. When it receives a request, it responds with the TCP/IP port number for the requested named instance. The client then uses this information to connect to the correct port number.

Yes. For clusters, you should install SQL Server Browser on each node in the cluster, but you should only start the service on one node at a time. It can run on any node at any given time.

You can enable SQL Server Browser during the installation process of SQL Server. Alternatively, use the SQL Server Configuration Manager or Services console to enable the service and set it to start automatically.

SQL Server Browser only responds to UDP requests from clients on the same subnet, so it cannot be exploited remotely. However, it does open a port on the machine it runs on, which represents a potential attack vector. Additionally, it requires elevated permissions to run, which could also pose security concerns.

Yes. If you rename a SQL Server instance that is using a static TCP/IP port, you should also update SQL Server Browser to reflect the new name and port number combination.

Yes. Disabling SQL Server Browser is an excellent way to reduce the overall attack surface of your system. It is often used as part of defense-in-depth security strategies in enterprise environments.

SQL Server Browser is available in all versions of SQL Server starting with SQL Server 2005.

You need to add an exception for UDP port 1434 and TCP port 2382 to allow traffic to pass through the firewall. Additionally, you can restrict access to the SQL Browser service by creating an inbound rule that only allows access to the specific IP addresses that are authorized to connect.