February 3, 2002 at 9:29 pm
If using MDAC 2.5 or earlier you may find that you can't connect to a named instance of SQL 2000. This is certainly the case if you have had client machines using MDAC 2.1.
There is a work around if you can't upgrade to MDAC 2.6 or later.
Edit the named pipe on the client machine to read :
\\servername\pipe\MSSQL$in1\sql\query
where in1 is the named instance from represented by the format servername\in1
This is valid obviously for named pipes not TCP/IP.
February 3, 2002 at 9:35 pm
But from a performance perspective, if the client isn't on the same system as the SQL Server, TCP/IP has the best performance of the network libraries. One of the problems with Named Pipes is it is a shared memory library, which works great locally but not so hot across the network. Obviously, local to a SQL Server 2000 instance would also means MDAC 2.6.
In the case of clients with MDAC 2.5 or lower who want to connect to a named instance via TCP, there are two methods:
1) If SQL Server 7 Client Tools are installed, go into Client Network Utility and set up an alias, pointing to the port of the named instance (chosen randomly at installation unless specified, so it'll have to be looked up per instance, per server)
2) If connecting through ODBC, choose Client Configuration, and set the port accordingly.
K. Brian Kelley
http://www.sqlservercentral.com/columnists/bkelley/
K. Brian Kelley
@kbriankelley
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply