Viewing 15 posts - 16 through 30 (of 30 total)
logicinside22 (4/11/2012)
This service broker query consumes high CPU above 80% and ave duration is 285 sec.
WAITFOR(RECEIVE conversation_handle, service_contract_name, message_type_name, message_body FROM ExternalMailQueue INTO @msgs), TIMEOUT @rec_timeout
Any idea...
November 14, 2012 at 1:51 am
I solved the problem. 😀
If anybody ever comes to CPU 100% usage problem, which can't be explained by classic reasons like bad queries, here is one more possible reason that...
October 17, 2012 at 2:06 am
GilaMonster (9/29/2012)
One more interesting thing, I started re-indexing job manually, when SQL Server was working OK. Then, after re-indexing job is finished, CPU started to go on 100% again. I...
October 14, 2012 at 2:58 am
Sean Lange (10/11/2012)
I seem to have steered you off topic.
No, I really appreciate because you spent your time to think about my problem. Thank you.
Sean Lange (10/11/2012)
October 11, 2012 at 10:16 am
Sean Lange (10/11/2012)
In your case you are processing 200 rows and it takes 2 hours. That screams of a serious need of performance tuning. I bet you can make this...
October 11, 2012 at 9:54 am
Sean Lange (10/11/2012)
Boris Pazin (10/11/2012)
Sean Lange (10/11/2012)
October 11, 2012 at 9:15 am
Sean Lange (10/11/2012)
October 11, 2012 at 8:47 am
I found something interesting.
Shrink job is running before the re-indexing job. That is not good.
I suppose it should be database shrinking first, re-indexing after, right?
One more interesting thing, I started...
September 28, 2012 at 5:37 pm
Ok, that mystery is solved, thanks again :cool:, but I still have that daily outages.
Every day, in almost same time, SQL Server takes 100% of CPU and not going down...
September 28, 2012 at 10:46 am
GilaMonster (9/27/2012)
Boris Pazin (9/27/2012)
The problem is that current queries are scripts for creating procedures, not for executing them.
The procedures are not being created. They are being executed.
When you execute a...
September 27, 2012 at 8:16 am
GilaMonster (9/27/2012)
Boris Pazin (9/27/2012)
The problem is that current queries are scripts for creating procedures, not for executing them.
The procedures are not being created. They are being executed.
When you execute a...
September 27, 2012 at 7:53 am
GilaMonster (9/27/2012)
The stored procedures are not being recreated. They're being executed.Find the worst performing code, tune it. Repeat until performance acceptable.
Gila,
thanks for replay.
Website is using procedures for showing...
September 27, 2012 at 7:42 am
D.Post (9/27/2012)
If you have access to SSMS 2008 you can right click on the instance name and select Activity Monitor.This will give you a good place to start troubleshooting.
I...
September 27, 2012 at 7:39 am
anthony.green (9/27/2012)
Restarting SQL is not a good idea as it flushes it's cache and when it restarts has to build the cache again which makes performance worse (usually)
It is production...
September 27, 2012 at 7:28 am
Viewing 15 posts - 16 through 30 (of 30 total)