SQL Server Home
SQL SERVER 2008 instance name
as By Design
4/2/2009 2:27:28 AM
User(s) can reproduce this bug
I have the following problem, i think its a bug in SQL SERVER 2008:
I have a Domain with one sql server installed on W2K3 SP2, with many sql
server and express installed on XP SP2, the overall number is 40, all are
2008 entriprise RC0 or 2008 advanced express (all are using single instance per device, some of them are using default instance name and other are using named instance named). My problem is that, the instance name can some time not appear in the SQL
server management studio and some time is appeared. I checked the browser
services, all are working well with domain administrator account. The
TCP,named pipe,shared memory all are active and working and the UDP broadcast is enabled on CISCO switches and the firewalls are disabled. I think the
problem is with the number of server/express per domain or its a bug. i think the number of sql servers per domain affect the overflow of browser servers.
I read about this issue several MS doc's. some of them said this is a bug.
but when he described the bug he said it can be solved by adding the sql
servers to AD. I added one SQL server on w2k3 to AD (This makes the problem solved if we are trying to browes the instance names from SQL management studio
but when the developers try to discover servers by using V.B6 + DMO its still not working).
Other servers on XP are not added to AD since i can not add those servers/express even when i implement the procedure discribed by MS.
best regards and thanks
SQL Server 2008 - Enterprise Edition
Tools (SSMS, Agent, Profiler, etc.)
Win2003 Enterprise Server (SP2)
Operating System Language
Steps to Reproduce
several steps are taken as discribed above.
No complete results.
I think its a bug, and i think the best way to solved by making the browser services and VB6_DMO searching in AD at first.
to post a comment.
Please enter a comment.
on 10/21/2010 at 6:10 AM
Yes, This is by design. Even if the UDP broadcasts are allowed, if the response from the target server
doesn't come back with-in 3 seconds, then that server is not part of the enumerated
list -- See KB article Q885345(this is for SQL 2000 but applies to other versions). This is also one of the reasons why the server
list keeps changing between enumerations calls.
Network infrastructure, especially routers, might limit the effect/visibility of
the broadcast, since most routers are configured not to relay broadcast request to
the other side of the router.
. SQLBrowseConnect does not allow us to specify the domain we want to search in, so
it searches in the domain that the client is in. Keep in mind the limitation of
step above. Because of routers, etc. it may not be able to find all SQL Server
instances in that domain.
I know this is late but never too late.
on 5/24/2009 at 11:49 PM
At all time the complete list of servers names and instances names are not appared from Management studio and VB.6 DMO (on W2K3 and XP SP2 ). some times it appears partially.
on 5/24/2009 at 11:11 PM
Thanks for reporting this issue. Are you stating that, sometimes you are able to see the list of servers and sometimes you arent, or you are seeing wrong or partial server names.
to post a workaround.
Please enter a workaround.
© 2013 Microsoft