Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
megbot
Starting Member
17 Posts |
Posted - 2008-04-21 : 14:13:43
|
I have a site that is experiencing the issue described in this doc. I'm unsure if the fix is going to blow anything up as I am unfamiliar with anything they are recommending.http://support.microsoft.com/kb/931279exec sp_configure 'affinity mask', 0x00000003GOreconfigureGO Any insight? Thanks,Meg |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2008-04-21 : 14:23:26
|
| Your best bet is to test it in a test environment first.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/ |
 |
|
|
megbot
Starting Member
17 Posts |
Posted - 2008-04-21 : 14:48:27
|
| definitely our plan, I was rather curious for a simple explanation as to what I'm changing, and if there are any obvious caveats to check for first. The Microsoft example is a bit technical for me. Or, if you possibly know of any other cause of this:The time stamp counter of CPU on scheduler id 2 is not synchronized with other CPUs.We get that here and there when the server is getting ready to go down for its scheduled reboot, it's hanging when trying to kill the SQL process. There isn't anything connected to it when it tries, I'm just at a loss, I've never seen anything like this, and the closest explanation found was that Microsoft article my accomplice found. |
 |
|
|
|
|
|