Viewing 15 posts - 16,246 through 16,260 (of 22,219 total)
I just started on the "good" plan, and it's all scans, not a seek in the process. There's missing index information:
/*
Missing Index Details from Clarks Unique Orders @ 26-OCT-2009 good.sqlplan
The...
"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
October 26, 2009 at 9:32 am
Even before I look at the execution plan, why are you doing this instead of an equals?
s.CampaignID IN (53)
"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
October 26, 2009 at 9:24 am
huston.dunlap (10/26/2009)
"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
October 26, 2009 at 7:43 am
Best thing you can do is get the actual execution plan for a good performing version and a bad performing version. The differences between the two are where the problems...
"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
October 26, 2009 at 7:37 am
There are a lot of ways you can do it and a lot of different types of performance tests. Are you trying to do a performance test based on the...
"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
October 26, 2009 at 7:10 am
Excellent introduction. Nice job Gail. Couldn't ask for better.
"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
October 26, 2009 at 6:13 am
sarvesh singh-457805 (10/25/2009)
Hi Grantlooking at the execution plan whichs tables do you think needs indexes.
For an execution plan that large, a complete break-down and set of recommendations would become billable...
"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
October 25, 2009 at 2:40 pm
sarvesh singh-457805 (10/24/2009)
I did run sp_updatestats to update the statistics. Do i have to update the statistics again. As far as missing index is concerned...
"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
October 25, 2009 at 12:17 pm
Jack Corbett (10/23/2009)
"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
October 25, 2009 at 12:11 pm
Jeffrey Williams-493691 (10/23/2009)
fred2002 (10/23/2009)
i explained it wrong.
first we restricted the size to 300MB
But now due to the errors we allw it to 1.2GB.
MS advise to fix a max size for...
"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
October 23, 2009 at 6:17 pm
Oh gosh, you're joining and unioning on views. That's potentially the cause of the problem right there.
Looking at the execution plan you've got about 12 different scans, several key lookups...
"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
October 23, 2009 at 6:14 pm
Piotr.Rodak (10/23/2009)
This would be SQL 2008 Grant 😉Regards
Piotr
Oh nuts am I bleeding over again? How come everyone doesn't just upgrade to 2008 and be done with it. It'd sure be...
"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
October 23, 2009 at 12:47 pm
It really depends on data integrity. If you're dealing with what is essentially unstructured data, then yes VARCHAR(MAX) is the way to go. If you've got a structure, then no,...
"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
October 23, 2009 at 6:54 am
Since you're posting this in the 2005 forum, you could use the Date data type. It's only 3 bytes. That's one less than smalldatetime and 5 less than datetime.
"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
October 23, 2009 at 6:48 am
There's nothing immediately obvious in the query that would suggest a performance bottleneck. The hard coded values of "0" do beg the question, how selective is that data, are you...
"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
October 23, 2009 at 6:45 am
Viewing 15 posts - 16,246 through 16,260 (of 22,219 total)