Viewing 15 posts - 13,576 through 13,590 (of 22,227 total)
The thing is, your process is causing the blocking. I'd seek a solution by address the process. I think you're in a "Doctor, doctor, it hurts when I do this"...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 18, 2011 at 8:07 am
I'd refer to Itzik's book as well.
But, while you're waiting for it to arrive, there is some explanation here. Here's a bit more. None of this addresses it directly...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 18, 2011 at 7:57 am
Yeah, without a, pick your time period, 6 months/year/decade worth of transaction monitoring, there is no way to know what data was accessed.
If you're interested in what has been access...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 18, 2011 at 7:46 am
Unless I'm reading this wrong, 20gb is very small as databases go. I agree that seperating out the storage to different filegroups would allow you to break up the backup...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 18, 2011 at 7:39 am
So if I understand the process, you've got a query that inserts into Table A (prosumably selecting from other sources), selects from that table using some kind of aggregate query,...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 18, 2011 at 7:34 am
GilaMonster (1/17/2011)
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 17, 2011 at 4:05 pm
Kwisatz78 (1/17/2011)
Hi I am in a similar situation to you in that I am just getting into performance tuning. I have found this a great article:http://sqlcat.com/whitepapers/archive/2007/11/19/sql-server-2005-waits-and-queues.aspx
That is an excellent...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 17, 2011 at 4:04 pm
dajonx (1/17/2011)
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 17, 2011 at 4:02 pm
I'd suggest spending time over at Paul Randal's blog. Here's a link to articles on cache over there.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 17, 2011 at 3:30 pm
Try this. Instead of the COUNT statement, use an EXISTS statement. It will perform much better.
IF EXISTS (SELECT * from dbo.tbl_WhateverItWas WHERE Val1 = @Param1 AND Val2 = @Param2)...
Of course,...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 17, 2011 at 3:27 pm
Roy Ernest (1/17/2011)
Lots of people have talked very Ernestly to me regarding being Ernest all the time in everything I do... 😀
It is important to be Ernest.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 17, 2011 at 1:14 pm
Why do you think it's not related to management studio? The queries are retrieiving the amount of space available. Couldn't someone be running one of the standard reports from SSMS...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 17, 2011 at 12:53 pm
Yes and yes.
When you alter a stored procedure, the plan in cache, if there is one, is marked as invalid, so a new one is created the next time...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 17, 2011 at 12:05 pm
You can't access that DMV for a particular database. Best thing you could do would be to run multiple queries against sys.dm_exec_waiting_tasks as your queries are running to determine what...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 17, 2011 at 12:04 pm
I agree. Execution time is one of the most important. Not on your list is one of my other favorites, frequency of call. Your longest running proc may be called...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 17, 2011 at 11:58 am
Viewing 15 posts - 13,576 through 13,590 (of 22,227 total)