SQL Server 2008 Express Remote Connection

2

I have 2 servers (one physical and one local VM) in which one of them has SQL Server 2008 R2 Enterprise Edition (physical) installed and the other one (local VM) I have SQL Server 2008 Express Edition.

After facing problems with the remote connection in the Express version, I discovered that I should enable and run the "SQL Server Browser" service in addition to the other TCP / IP firewall settings.

My question is this: To remotely access the server with the Enterprise version I do not need to be running the SQL Server navigation service, since the Express version I need to leave it running. Would anyone know why this occurs?

    
asked by anonymous 28.08.2014 / 15:22

1 answer

1

According to the Technet :

  

The SQL Server Browser listens for incoming requests from the   features of Microsoft SQL Server and provides information about   Instances of SQL Server installed on the computer

The difference between Express installations of conventional ones is that by default SQL Express uses an instance named SQLEXPRESS . The other edits use the default instance name MSSQLSERVER , which instance can be omitted when accessing the server remotely.

Because the physical instance is not named and enabled on the default port (1433), after the Firewall and TCP / IP are released, it is ready for use and does not require the Navegador do SQL Server service enabled. p>

According to this question from the dba.stackexchange , this service is disabled by default because of a denial of service threat called SQL Slammer .

    
28.08.2014 / 18:30