Re: Server Discovery Instance Name Problem
- From: "Rick Byham [MS]" <rickbyh@xxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 6 Jun 2006 09:50:56 -0700
SQL Server 2000 became aware of SQL Server Browser with SP3. Perhaps you
have older versions. They don't know how to share.
--
Rick Byham
MCDBA, MCSE, MCSA
Documentation Manager,
Microsoft, SQL Server Books Online
This posting is provided "as is" with
no warranties, and confers no rights.
"PaulJB PHD" <ThePhage@xxxxxxxxxxxxx> wrote in message
news:ED4258F4-BBAC-4DB2-BBD1-DC201ADEEE50@xxxxxxxxxxxxxxxx
We recently installed SQL Server 2005 on machines that also had SQL Server
2000 present. When the SQL Server Browser service is running on any of
these
machines, ALL machines on our network start having a problem detecting the
names of SQLServer instances from SQL Server 2000 applications (Enterprise
Manager, Query Analyzer, or Service Manager) and through SQLDMO. The name
of
machines running SQLServer are retrieved in the discovery list, but the
Instance name does not appear.
For example, lets say I have two machines running SQL Server:
On machine ALPHA, SQLServer is the default instance
On machine BETA, SQLServer has an instance name of BACKUP
If ANY machines with both SQL Server 2000 and SQL Server 2005 have the SQL
Server Browser service running, these machines would be enumerated as:
ALPHA
BETA
If the SQL Server Browser service is shut-off on ALL of the machines, the
machines would be enumerated as:
ALPHA
BETA\BACKUP
Other things of note:
- When SQLServer 2005 was running on a machine by itself, the Server
discovery behaved normally. We had 2005 SQLServer running on a 2003 Server
and a Windows XP virtual machine for several months without a problem.
- Turning the firewall on a machine running the SQL Server Browser
service,
also solves the problem. If the SQL Server Browser service is entered as
an
exclusion in the Firewall, the problem appears.
- SQLServer discovery via SQLServer 2005 applications (SQL Server
Management
Studio) or methods (.NET 2.0 Sql.SqlDataSourceEnumerator) behaves normally
and can retrieve Instance names even when the SQL Server Browser service
is
running.
Currently we have the SQL Server Browser service disabled on all the
problem
machines. How can I fix this issue while still having the SQL Server
Browser
Service running?
Thanks.
--
PaulJB PHD
.
- Prev by Date: txn isolation level and connection pooling
- Next by Date: Re: SQL Server 2005 Express Connection
- Previous by thread: txn isolation level and connection pooling
- Next by thread: Re: Sharing databases netween SQL 2000 and 2005
- Index(es):
Relevant Pages
|
