following on from http://www.experts-exchang
I installed a new (named) instance on one of our PCs. It's working perfectly, after tweaking the settings manually as described in the above question.
However, when I go to another PC, something strange is happening. I go into SQL Server Management Studio (in my case I have "SQL Server Management Studio Express CTP", whatever that is) and it prompts to connect to a SQL Server Instance. When I browse for instances on the network, I can see several Named instances on several other PCs. But from the PC on which I just installed a new Named Instance of SQL Server Express, I only see the default instance. As I try to start and stop services, sometimes even THAT disappears. But I sure as heck never see the named instance.
Funny thing is, if I ignore the Browse dialog, and I type in the exact name of the Named Instance, knowing what it SHOULD be, it connects just fine.
Ze mind ist boggling ja?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Yes, I think you're right. Having said that though I don't think that that is the problem. I have googled for "not returning named instances" and it looks like this is a well known problem. I have yet to find a solution. The "good" news though is that it doesn't appear to be a problem with the embedded install I created, but the problem is client based.
Ok. I think this is the reason. The "default" instance is likely to broadcast on the standard TCP/IP port, and that is why it is being picked up by utilities such as oSQL -L
Any additional "named" instances would use dynamic TCP/IP ports and would not be visible to the user.
Here is what I did to solve the problem:
I use SQLDMO.Application to list all instances. After that, I iterate through the instances. I connect to each instance I find, and if the connection succeeds, I ask it to tell me what instances are present, basically by invoking:
EXEC master..xp_regenumvalues 'HKEY_LOCAL_MACHINE', 'SOFTWARE\Microsoft\Micros
I then add anything I find in there over and above the default of MSSQLSERVER as SERVERNAME\INSTANCENAME
And bob's yer uncle.
Business Accounts
Answer for Membership
by: Olaf_DoschkePosted on 2009-09-23 at 03:28:15ID: 25401442
CTP means community tech preview, which is a beta version. You should uninstall that and install the real SQL Management Studio Express version.
Bye, Olaf.