patternsqlMinor
SQL Server Connectivity Issues
Viewed 0 times
sqlissuesconnectivityserver
Problem
I am getting the below error on occasion. Maybe every 30mins or so. I am not sure how to track what is causing the issue. I think it could be a Network problem as there are disk backups running as well.
Any suggestions on where to begin? Thanks!
The underlying provider failed on Open. ---> System.Data.SqlClient.SqlException: A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: SSL Provider, error: 0 - The wait operation timed out.) ---> System.ComponentModel.Win32Exception: The wait operation timed out
Any suggestions on where to begin? Thanks!
The underlying provider failed on Open. ---> System.Data.SqlClient.SqlException: A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: SSL Provider, error: 0 - The wait operation timed out.) ---> System.ComponentModel.Win32Exception: The wait operation timed out
Solution
OK, so odds are it isn't link that Up_One posted.
SQL Server does all it's work via schedulers. Each scheduler is attached to a CPU core on the server. Usually when I've seen that error it's because the CPUs are very busy and can't properly respond to the request in the time needed.
What's the CPU workload on the SQL Server look like when the problem happens? How many users are running queries at that time? How many CPU cores does the server have?
The fix is to reduce the CPU workload on the server. Typically this is done by doing index tuning on the system which will reduce CPU workload.
SQL Server does all it's work via schedulers. Each scheduler is attached to a CPU core on the server. Usually when I've seen that error it's because the CPUs are very busy and can't properly respond to the request in the time needed.
What's the CPU workload on the SQL Server look like when the problem happens? How many users are running queries at that time? How many CPU cores does the server have?
The fix is to reduce the CPU workload on the server. Typically this is done by doing index tuning on the system which will reduce CPU workload.
Context
StackExchange Database Administrators Q#57455, answer score: 6
Revisions (0)
No revisions yet.