One for the sql experts

I believe there is a bug with sql EE and the SQL surface area configuration tool.

Basically I was running SQL Server 2005 standard edition for general visual studio development. The servcie name for the sqlserver instance is MSSQLSERVER and the display name is SQL server (MSSQLSERVER). Now recently i installed WSS3.0 (the server previously had no instance of windows sharepoint services). When WSS 3.0 installed it installed the sql server embedded edition instance. So now I have 2 sql instances on the server. One named MSSQLSERVER and the other named MICROSOFT##SSEE which are the names taken from the sql server configuartion manager. HOWEVER if i go back into the SQL server 2005 surface area configuartion tool and launch "Surface are configuration for services and components" whilst the name and display name hasnt changed for the MSSQLSERVER instance there is an inconsistancie with the MICROSOFT##SSEE instance. The service name displays as MSSQL$MICROSOFT##SSEE. Now the problem is if I launch "surface area configuartion for fetures" it complains it cant connect to localhost\MICROSOFT#SSEE because remote connections are not enabled. However both named pipes and tcp/ip are allowed and in the surface area configuartion tool remote connections are allowed for that instance. Does the surface are configuration for features connect to the sql instance using the display name or service name ? because if its the service name surely it should be connecting to MSSQL$MICROSOFT##SSEE and not MICROSOFT#SSEE ? if this is the problem how do i rename the service name from MSSQL$MICROSOFT##SSEE to MICROSOFT#SSEE ???

The SSEE is a special version of MSDE that can only be used by WSS3, it extends the database limit and allows many more connections.

Only WSS3 can connect to it - this includes tools like Query Analyser and Surface Area Config.

not true. In the surface area config you have "Surface are config for services and connections" and "surface area config for features". SACFSAC connects fine to both the MSSQLSERVER and MICROSOFT#SSEE whereas SACFF attempts to connect but bottoms out with an sql error 26 with remote connection, whereas I explicitly know remote connections are allowed. Like wise any computer in the network cant remotely connect to that MICROSOFT#SSEE instance because the problem as i see it the instance name here is MSSQL$MICROSOFT##SSEE ???

for example here is SACFSAC

http://img338.imageshack.us/img338/2553/picture1mb6.jpg

NOTICE microsoft#ssee and mssql server both appear !!!

here is SACFF

http://img338.imageshack.us/img338/8226/picture2lq4.jpg

This screen stays up for about a minute trying to connect to both instances however it eventuallt fails

http://img338.imageshack.us/img338/7010/picture3yr7.jpg

BUT REMOTE CONNECTIONS ARE SET FOR BOTH TCP/IP AND NAMED PIPES !!!! grrrrr very frustrating. Why WSS installs embedded edition , why cant it just create a new instance in mssqlserver ? if i stop MICROSFT#SSEE in the sql configuartion manager i am able to get back into SACFF !!

finally found the answer to the problem

1st step was to go into sql server config manager > right click MICROSOFT#SSEE > Hide Instance change from yes to no

2nd step is to go into surface config area > set remote connections for MICROSOFT#SSEE for TCP/IP AND NAMED pipes.

I can now connect remotely to MICROSOFT#SSEE via SQL management studio.

There should be something in the Sharepoint 3.0 documentation about this as the default install renders surface area config manager useless