Tech Support Guy banner
Status
Not open for further replies.
1 - 2 of 2 Posts

·
Registered
Joined
·
1 Posts
Discussion Starter · #1 ·
I am evaluating a new web hosting firm. They seem good, but they have SQL 2000 servers. I run SQL 7 on my current machine. I can connect to the new database server fine with ASP through an ODBC DSN, but I cannot figure out how to connect via Enterprise Manager, Query Analyzer, or even Access 2000.

It is going to be a real hassle uploading data without EM or one of the other tools. Microsoft says that connecting via SQL 7 clients should be possible, but I do not understand this information:

[When using the SQL Server client connectivity components from SQL Server 7.0 or earlier, you must set up an alias using the Client Network Utility before you connect to a named instance of SQL Server 2000. For example, on a SQL Server 7.0 client, to connect to a named instance of SQL Server 2000, you must add an alias that points to \\computername\pipe\MSSQL$instancename\sql\query. If you use an alias name of computername\instancename, clients can connect by specifying this name in the same way as SQL Server 2000 clients do. For the TCP/IP Sockets and NWLink IPX/SPX Net-Libraries, you must use the Client Network Utility to define an alias on the client that specifies the port address on which the named instance is listening.]

Can anyone enlighten me? Thanks
 

·
Registered
Joined
·
140 Posts
Yes, you can either Add a system DSN for your server, or go into start>programs>mssql7>client network utiliity and create an alias for that server. If you use named pipes, you need to configure one that shows what pipe that server is and the server name. If you are on TCP/IP you just need to add that server name, the IP and port number (usually 1433). If you go to the client network utility, it should be fairly self explanatory. After you add this there, you should be able to connect with enterprise manager.
Hope this helps
--Adam
 
1 - 2 of 2 Posts
Status
Not open for further replies.
Top