February 15, 2012 at 2:40 pm
We have a new 2 node windows cluster (win 2008, sql 2008r2). Recently the SQL instance was moved to node 2 in the cluster (after the Windows admin applied OS patches). The SQL Agent began performing very slowly, Jobs which normally execute in couple seconds needed 3 minutes to complete, jobs normally finishing in 10 minutes needed an hour to complete. This poor performance continued until we moved SQL resources back to node 1, so basically Agent performance on node 2 stinks. I'm thinking there may be a difference in configuration in the 2 nodes. Any ideas what i can check? Below is the errors from SQL Agent Log.
[165] ODBC Error: 0, Unable to complete login process due to delay in opening server connection [SQLSTATE 08001]
[165] ODBC Error: 0, Login timeout expired [SQLSTATE HYT00]
[298] SQLServer Error: 258, TCP Provider: The wait operation timed out. [SQLSTATE 08001]
[264] An attempt was made to send an email when no email session has been established
February 15, 2012 at 8:57 pm
Once you move to problem node , close the Faliover CLuster Manager and on re-open does it take more than 30 seconds to populate the SQL server instance ?
Also going by error message seems the performance is slow on that node, this is Windows cluster performance issue in some cases rebooting the node helps but if that does not help please check with you Windows administrator
Cheers
Sat
Cheer Satish 🙂
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply