Activity overview
Latest activity by hcDBA
Just a follow-up: we installed SQL 2008 SP4 on that server (after testing on our dev servers) and that fixed the issue. Thank you! / comments
Just a follow-up: we installed SQL 2008 SP4 on that server (after testing on our dev servers) and that fixed the issue. Thank you!
Yes, that server is running SQL Server 2008 SP1 (it's scheduled to be upgraded later this year). I will check it out. Thank you! / comments
Yes, that server is running SQL Server 2008 SP1 (it's scheduled to be upgraded later this year). I will check it out. Thank you!
We are also using 7.1.20.11693, so we are on the same version. We have been good for about 7 hours now since the last reboot, and we are not going add it back to SQL Monitor, because we are trying to isolate the cause (for the last several reboots, it was being monitored by SQL Monitor, so we want to see if keeping it off will prevent the high CPU issue). / comments
We are also using 7.1.20.11693, so we are on the same version. We have been good for about 7 hours now since the last reboot, and we are not going add it back to SQL Monitor, because we are trying...
We have the exact same problem with one of our servers. It keeps hitting 100% CPU, and there are several processes running xp_readerrorlog that have wait types of PREEMPTIVE_OS_GETPROCADDRESS. We don't have hundreds of them like the case above, but it would reach hundreds if we let it keep accumulating. We end up having to reboot and the problem continues to arise. In the meantime, we have had to suspend monitoring by SQL Monitor on that server. I am going to put in a support ticket and hope the support staff can figure it out, but just wanted to give everyone a heads up that this is not an isolated case - we're getting it, too! / comments
We have the exact same problem with one of our servers. It keeps hitting 100% CPU, and there are several processes running xp_readerrorlog that have wait types of PREEMPTIVE_OS_GETPROCADDRESS. We...