Can't connect SQL Server 2000 clients to SQL Server 2005 Database

[djpingpong]

Hi all,

I recently put in a new database server at work running Windows 2000 Professional with SQL Server 2005.... I'm a newbie to SQL Server 2005, so please assume I know nothing about it.
We also have 2 other Win2k machines running SQL Server 2000

Here's my issue:
I've got a database on SQL Server 2005 named "Weld"
On all the other workstations at work, we also run Windows 2000 and most of them have SQL Client tools installed on them.

With Enterprise Manager (on any of the client machines), I can't connect to the database on the SQL Server 2005 machine, but I can still connect to the other database servers running SQL Server 2000.

Now, do I have to downgrade my SQL Server 2005 back to 2000... or is there a better solution? I have a feel that it's probably some setting in the "SQL Server Configuration Manager", but i don't know exactly what...

 

[ptheriault]

You can't connect to a 2005 database instance with the 2000 tools. You can install the 2005 tools on a client with 2000 tools. the client tools are completely separate from each other.
You can use SQL 2000 Query analyzer to connect to a 2005 instance but why would you want to. The 2005 tools are pretty good.

- Paul
- Database performance looks fine, it must be the Network!

 

[SQLBill]

SQL Server 2005 version of Enterprise Manager (EM) is SQL Server Management Studio (SSMS). And while you can't view a 2005 instance with EM, you can view 2000 instances with SSMS.

-SQLBill

Posting advice: FAQ481-4875

 

[mrdenny]

You also need to tell the SQL 2005 install that it may accept remote connections.

Denny
MCSA (2003) / MCDBA (SQL 2000) / MCTS (SQL 2005) / MCITP Database Administrator (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

 

[djpingpong]

You can't connect to a 2005 database instance with the 2000 tools. You can install the 2005 tools on a client with 2000 tools. the client tools are completely separate from each other.

Well, since all our development is still mostly done in SQL Server 2000... I think ptheriault has convinced me to just do what i wanted to initially...which is to convert the SQL Server 2005 machine back to SQL Server 2000 to conform with the rest of the machines....

I rather do that than have to upgrade everything to sql server 2005...

 

[mrdenny]

Your dev systems should be the same version as your production systems. If you don't have SQL 2005 in production, and you aren't moving in that direction, then a SQL 2005 dev server isn't of much use to you as it's not a like enviroment to your production system and code that works in SQL 2005 but not in SQL 2000 could get moved to production.

If you want to keep the SQL 2005 server you can install the SQL 2005 tools side by side with the SQL 2000 tools.

You can also use the SQL 2005 tools to manage a SQL 2000 server.

Denny
MCSA (2003) / MCDBA (SQL 2000) / MCTS (SQL 2005) / MCITP Database Administrator (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com