• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1166
  • Last Modified:

Connecting SQL Server Management Studio to SharePoint Database

I'm trying to connect Management Studio to the SharePoint database.

I have gone to the server and given the MSSQL$MICROSOFT##SSEE database an alias of SharePoint using TCP/IP protocol and port 1433 through SQL Server Configuration Manager and through SQL Server Surface Area Configuration I have configured it to use TCP/IP remote connections only.

When I browse for network servers through Management Studio however, the database only shows up as "Server\MICROSOFT##SSEE" (i.e. not the alias name) and when I try to connect to it I get an error that reads:

"A network-related or instance-specific error occurred while establishing a connection to SQL Server.  The server was not found or was not accessible.  Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 28 - Server doesn't support requested protocol) (Microsoft SQL Server)
0
itsupport1199
Asked:
itsupport1199
  • 6
  • 6
  • 2
2 Solutions
 
Justin SmithSr. System EngineerCommented:
You are aware this isn't technically a SQL instance, correct?  It's the Windows Internal Database.

http://www.mssqltips.com/tip.asp?tip=1577
0
 
itsupport1199Author Commented:
Yes.  I am.  It was my understanding, though, that I could connect to it through Management Studio.

This seems to imply that I need to register the service under a different name.  How would I go about doing that?  
0
Fill in the form and get your FREE NFR key NOW!

Veeam is happy to provide a FREE NFR server license to certified engineers, trainers, and bloggers.  It allows for the non‑production use of Veeam Agent for Microsoft Windows. This license is valid for five workstations and two servers.

 
itsupport1199Author Commented:
Can reregistering the service cause any issues with SharePoint?
0
 
itsupport1199Author Commented:
Hi Zephyr,

I've done all that.  Still no luck.  
0
 
Justin SmithSr. System EngineerCommented:
you need to connect using the string from the link i posted.....
0
 
Justin SmithSr. System EngineerCommented:
\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query

No it won't affect SP if you register this name.
0
 
zephyr_hex (Megan)DeveloperCommented:
you dont need to register the service under a different name.  it should be just a matter of following the steps in the link i posted.

you may also want to try the connection string listed here:
http://tedonsharepoint.blogspot.com/2009/07/named-pipes-connection-string-for-sql.html
0
 
itsupport1199Author Commented:
I'm not clear on how I register that name.  
0
 
itsupport1199Author Commented:
I've gone through the steps Zephyr posted and I've tried connecting using the string provided by ACH1LLES.  Still no luck.

Does it make a difference that I'm trying to connect remotely and not on the actual SQL Server?
0
 
Justin SmithSr. System EngineerCommented:
I've only done it locally....so see if it works locally first.  You'll need to be a local admin.
0
 
Justin SmithSr. System EngineerCommented:
also, since this uses named pipes, you need to enable remote conections on the named pipes protocol through SQL config
0
 
Justin SmithSr. System EngineerCommented:
so you tried connecting locally, on the server, using an admin, and it won't connect??
0
 
itsupport1199Author Commented:
I was unable to resolve the issue, but the need has passed.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 6
  • 6
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now