Connecting to SQL Server Through Query Analyzer

Richard Waymire answers a reader’s question about problems using Query Analyzer to log in to SQL Server.

Richard Waymire

August 21, 2001

1 Min Read
ITPro Today logo in a gray background | ITPro Today

Since I installed the SQL Server 2000 tools on my PC, I've had problems using Query Analyzer to log in to my SQL Server 2000, 7.0, and 6.5 servers. Establishing a connection takes a long time, and in most cases, several tries. I frequently receive the error message ODBC SQL Server Driver Timeout expired. I've increased the logintimeout value in both Enterprise Manager and Query Analyzer to 45 seconds, but I still get the timeout error after only 15 to 20 seconds, not 45. When I use the SQL Server 6.5 isqlw utility, I always get a connection right away. What am I missing?

Are the SQL Server 7.0 and 6.5 servers using named pipes only? If so, the problem might be that your SQL Server 2000 client is trying to use TCP/IP sockets by default. You can go into the Client Network Utility on your client machine and reset the default network protocol to named pipes. Alternatively, you can follow Microsoft's strategic direction by adding TCP/IP sockets to your SQL Server 7.0 and 6.5 servers.

Sign up for the ITPro Today newsletter
Stay on top of the IT universe with commentary, news analysis, how-to's, and tips delivered to your inbox daily.

You May Also Like