Client Network Utility

[EscapeUK]

I have 2 database servers. One database server is "live" and the other is used for testing.

To connect to the live database the clients use Microsoft Data Link and MTS. Due to the way the system is set up it is not possible to set up a data link on the client PC's to the test server.

What we have to do is use the client network utility on the live server.

Could you tell me if any problems will arise if I add a server alias pointing to the test server. I need to leave the default connection as Named pipes and set the alias to TCP/IP. The users will be accessing the live database while others at the same time will be accessing the test database.

Is that OK and what does the client network utility do and how does it work on a server.

 

[foxdev]

Wow, I've read your post several times and I'm still not sure what you are trying to do. Let me just dump and you can see if any of it helps:

The Client Network Utility, run on the client machines, allows the designation of the one protocol (I use it to switch from the default Named Pipes to TCP/IP) that will be used to connect to the server, and it can be used to define a server alias in the event that you do not wish to use the actual UNC name or IP address.

SQL Server Network Library Configuration, run on the server, allows you to designate multiple protocols, so that the server will "listen" on each of them. In other words, the server can be configured to listen on Named Pipes, TCP/IP, and IPX. Different client machines can connect to that server using any of the protocols on which the server is listening, but each client uses only one of the protocols.

Using the Client Network Utility you can assign an alias to a server, but I don't think you can have the alias use a different protocol, since it is in actuality the same server.

I don't see that the C.N.U. is going to help you somehow connect to the Test server via the Live server.

Robert Bradley

http://www.foxdev.com/