November 5, 2010 at 4:31 pm
This is a question and answer post, as I have spent about week searching for answers on and off line. Finally, got the answer by accident. Just want to document this here for anyone who might have the same issue and save them some time.
I have two instances of SQL on a 3-node cluster. Both instances self-restarts about 1 to 3 times a day, restart was successful, so no failover. The cause for this problem is that someone checked the Server Properties->Processors->Boost SQL Server Priority in the server configuration.
By Googling Boost SQL Server Priority, I came across the following documents that actually detailed my problem.
http://msdn.microsoft.com/en-us/library/aa196713(SQL.80).aspx
November 5, 2010 at 4:34 pm
meant to add the following point to the original post. all sources I came across from initial research links the communication link failure error to network issue, well, it could be, but the above check is quick and easy to eliminate Boost SQL Server Priority as an issue.:-)
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply