SQL Server Performance Forum – Threads Archive

Requirement to use Management Studio

What are the requirements to use Management Studio/Management Studio Express for local instances? Are the requirements same for both studios and same for all OS?
Based on my own testings:
Remote connection is required for Management Studio in Windows XP SP2.
But it is not required in Management Studio Express in Windows XP SP2. For Windows 2003 and 2000, remote connection is not required for Management Studio. Have not tried Management Studio Express yet. Peter

http://msdn2.microsoft.com/en-us/library/ms165690.aspx and also MSXML6 is required, so get it as a download….many software require later versions of XML. Satya SKJ
Microsoft SQL Server MVP
Contributing Editor & Forums Moderator
http://www.SQL-Server-Performance.Com
This posting is provided Ã¯Â¿Â½AS ISÃ¯Â¿Â½ with no rights for the sake of knowledge sharing.

Hi Satya, I’m testing the following in a Windows XP SP2 with SQL Server 2005 Developer Edition SP1: Scenario #1
1. Checked Local connections only in SSSAC for a SQL Server 2005 local instance
2. Restarted that instance in SSCM (Note: only Shared Memory enabled for Network Configuration)
3. Tried to connect to that instance in SSMS and get this error: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 28 – Server doesn’t support requested protocol) (Microsoft SQL Server, Error: -1) Scenario #2
1. Checked Local and remote connections and Using named pipes only in SSSAC for a SQL Server 2005 local instance
2. Restarted that instance in SSCM (Note: Shared Memory and Named Pipes enabled for Network Configuration)
3. Tried to connect to that instance in SSMS and get this error: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 28 – Server doesn’t support requested protocol) (.Net SqlClient Data Provider) Scenario #3
1. Checked Local and remote connections and Using TCP/IP only in SSSAC for a SQL Server 2005 local instance
2. Restarted that instance in SSCM (Note: Shared Memory and TCP/IP enabled for Network Configuration)
3. Tried to connect to that instance in SSMS and was able to connect
4. The following is fromt the SQL Server Logs: Server is listening on [ 127.0.0.1 <ipv4> 4906].
Server local connection provider is ready to accept connection on [ \.pipeMSSQL$SQL2005_AM7sqlquery ].
Server local connection provider is ready to accept connection on [ \.pipeSQLLocalSQL2005_AM7 ].
Server is listening on [ ‘any’ <ipv4> 2464]. What do they mean? Why I cannot connect to the local instance in Scenario #1 and #2?
Thanks for any help, Peter

]]>