I have about 20 sql servers (2000 and 2005). I setup an MSX/TSX job in
SQL Agent to Register the Server in Active Directory to make sure that
all future targets are registered, etc..
---Enroll the server in Active Directory
use [master]
go
exec sp_ActiveDirectory_SCP @Action = N'create'
go
However, 90% of my servers are NOT listed when I do:
osql -L
or try to choose any network SQL Server connection in SQL Server
Management Studio. All servers have TCP/IP and Named Pipes Enabled
and remote connectivity enabled (2005).
What can I do to ensure all of my servers can be seen and availble
from a drop down list of servers?
Thanks
Erik
Linchi Shea - 11 Mar 2008 02:05 GMT
Short answer is that you shouldn't count on osql -L to list all your servers.
It is not designed to do so.
Linchi
> I have about 20 sql servers (2000 and 2005). I setup an MSX/TSX job in
> SQL Agent to Register the Server in Active Directory to make sure that
[quoted text clipped - 20 lines]
>
> Erik
info@onlyhd.tv - 11 Mar 2008 21:34 GMT
But what about my list in Sql Management Studio, it barely has sql
servers listed in it.???
IanLowe77@googlemail.com - 14 Mar 2008 14:20 GMT
Hi Erik,
Do you have a mix of SQL Server 2000 and SQL Server 2005 servers? And
is it only the SQL Server 2005 servers that you cannot see?
I've found that at many sites, the SQL Server Browser service has not
been started on the SQL Server, so it can only be seen locally and not
across the network. Microsoft disables this service by default for
added security, so you need to start it manually after performing a
new installation of SQL Server.
Let me know if this helps.
Regards,
Ian Lowe
SQLServerClub.com