March 16, 2011 at 10:26 am
i installed ssms 2008 on a windows 7 pc, connection to sql 2008 instance is fine, but can't connect to any sql 2000 instances. also, the BID comes with SQL 2008 CD has problem connect to any sql 2000 instances. Do i have to install any OLEDB\ODBC driver? any idea?
_______________________________________________________________
March 16, 2011 at 11:24 am
SQL 2000 does not have a SQL Browser service like 2005+. Accessing it by IP address should work for you.
*I think* if you register the server name as a System DSN or as a Registered Server through SQL 2000 Enterprise manager (if you also have that installed) then SSMS can use that for name resolution.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
March 16, 2011 at 11:38 am
May be SP matters. I had the same issue with 2005 and 2008. installing latest SP on 2005 resolved my issue.
Thanks
Jagan K
March 17, 2011 at 11:07 am
i can't register the server as system DSN since my win7 pc can't recognize the server. however, i can ping that sql2000 server.
i tried to use ip\instance name (in both SSMS and system DSN), doesn't help.
don't want to install sql2000 em.
sp doesn't help, i am using sql2008 dev sp2.
_______________________________________________________________
March 17, 2011 at 11:13 am
I ran into a similar issue using Linked Servers to reach a MySQL DB, but it was on SQL 2005. The issue traced back a driver issue where it was not releasing Virtual Memory Space after a query ran and failed. The only way to clear the virtual memory space was to restart the SQL Server service.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
March 18, 2011 at 5:43 am
You should be able to connect to any SQL 2000 instance using your 2008 SSMS Client Tools regardless of whether you use the IP address or DNS resolution.
March 18, 2011 at 7:15 am
yes, it SHOULD.
i have another windows XP. ssms2008 has no problem connect to sql2000/2008.
but this windows 7......
_______________________________________________________________
March 18, 2011 at 7:24 am
Well i'm on Windows 7 using the SQL 2008 R2 Client tools and have NEVER had any problems connecting to any SQL 2000 instances.
Has this ever worked?
What messages do you get?
What do you mean by
michael wang-201906 (3/16/2011)
also, the BID comes with SQL 2008 CD has problem connect to any sql 2000 instances
March 18, 2011 at 7:30 am
never mind, i am going back windows xp, same PC with XP works fine. don't want to waste any more time on this.
Windows 7 just a fancy thing in office for me. btw, win7 xp mode works :hehe: but it's way too slow.:hehe:
_______________________________________________________________
April 9, 2013 at 4:04 pm
I had same issue , SSMS 2008 was not connecting to SQL 2000 server (Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 2) failed with server not found error , my guess is it might be service pack issue , I tried using SSMS 2005 , it worked fine 🙂
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply