We are having some connectivity issues from a client application connecting to a remote SQL Server 2005 (named instance).
What are some ways to test connectivity from the client machine (Windows XP) that doesn't have SSMS or Query analyzer installed?
I would like to see if the issue is related to the specific application or is it a more general connectivity to the remote sql server from the specific client.
My favourite is create a new text document on your desktop. Change the file extension to '.udl' - this creates a Universal Data Link file. Double click it and fill in the properties and use that to check for connectivity.
Obviously requires you to have the relevant client side network libraries installed.
answered Feb 12, 2010 at 06:04 PM
Kev Riley ♦♦