February 18, 201016 yr Office1 has SQL 2000 server Office2 connects to SQL 2000 server via a 10M fibre link User at Office2 are complaining of slow response times from the SQL server at Office1 TROUBLESHOOT: Run SQLDIAG on the Server to see if it is an Server vs. Connection issue. Stop and re-start the SQL Server. Click Start | Run | CMD Type SQLDIAG Press Enter. Follow any on screen commands. After the error occurs press Ctrl+C to stop SQLDIAG. Analyze the files (default location: C:\Program Files\Microsoft SQL Server\90\Tools\Binn\SQLDIAG) If you are using a packet capture tool like wireshark, you can filter for TCP/IP port 1433 which is traffic, by default, used by MS SQL Server.
Create an account or sign in to comment