November 29, 2010 at 9:15 am
Guys,
I have a situation in SQL 2008 (SP2) 64 bit where the CPU remains static at 35-40% consumed by SQL Server exe process, I have tried to check the processes consuming the CPU none of them
come from the queries against the user created databases.
SELECT * FROM sys.SYSPROCESSES
--where spid = 55
ORDER BY cpu DESC
lastwaittypecpu
PREEMPTIVE_XE_CALLBACKEXECUTE 173294828
LAZYWRITER_SLEEP 2568812
Is there anyway to find out what is causing high cpu (there are no sql jobs running during this time), any inputs or suggestions would be helpful.
Thanks
November 29, 2010 at 1:15 pm
I'm not overly familiar with the PREEMPTIVE waits, but the LAZYWRITER_SLEEP is just SQL waiting to run the next checkpoint.
Have you tried running sp_who2 during this time?
--------------------------------------------------------------------------
When you realize you've dug yourself into a hole....Step 1...stop digging.
November 29, 2010 at 1:22 pm
Direct quote from here: http://sqlblogcasts.com/blogs/christian/archive/2008/06.aspx
The first interesting ones I’ve looked at are the new PREEMPTIVE wait types. Any code that needs to execute outside SQL Server has to go outside the control of SQL Server’s co-operative (or non-preemptive) scheduler and will use the preemptive scheduling model used by the OS.
Typically these external executions would be very difficult to troubleshoot using wait types because they would either come under a single wait like OLEDB for example or wouldn’t be tracked at all like OS level functions. If you’ve ever tried to troubleshoot a SQL Server issue that turned out to be latency talking to the domain controller you’ll be presently surprised with the PREEMPTIVE_OS wait types that will show authentication waits
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply