Viewing 15 posts - 14,986 through 15,000 (of 22,219 total)
There really isn't anything "to do" with the tables. If you have lots of objects in your database, you're going to have lots of rows in the system tables. As...
"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
May 19, 2010 at 1:02 pm
Generally, you don't. I've never heard of anyone defragging a system index. Since you're operating in 2005/2008, you can't get direct access to the tables anyway, you're just looking at...
"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
May 19, 2010 at 10:51 am
No, when a plan is flushed from cache, it's gone forever. The only thing you can do is try to capture the plans regularly (based on how often they flush...
"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
May 19, 2010 at 10:50 am
It adds overhead, but it's pretty trivial. The accumulative effects aren't good, but you're unlikely to see any given query perform badly because of 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
May 19, 2010 at 10:48 am
Please, edit the post, remove the XML. Then go back and save your execution plan as a .SQLPLAN file. You can then post the file as an attachment. From 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
May 19, 2010 at 9:35 am
From the Books Online:
The missing indexes feature is on by default. No controls are provided to turn the feature on or off, or to reset any of the tables returned...
"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
May 19, 2010 at 9:33 am
Dynamic methods are frequently problematic, but to get the data you're looking for, check out the system views available under the schema called INFORMATION_SCHEMA. They should supply you with everything...
"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
May 19, 2010 at 8:19 am
To be able to use all the methods and abilities of 2008, you will need to set the compatibility mode to 2008, not 2000. Performance may or may not...
"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
May 19, 2010 at 8:17 am
Paul White NZ (5/19/2010)
Grant Fritchey (5/18/2010)
...while the other does a completely useless sort...
That sort on SchID is an optimisation for sequential I/O.
Look at the loop join after the sort operator...
"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
May 19, 2010 at 6:49 am
If you right click on the plan and "Save As" a .sqplan file, you can post this online so that we can see more information. But, you do have an...
"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
May 19, 2010 at 6:23 am
I freely admit I'm not smart enough to always figure out or understand why the optimizer did something. All I can say is what I see. The place where 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
May 19, 2010 at 5:16 am
J-F Bergeron (5/18/2010)
"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
May 18, 2010 at 1:51 pm
The difference I'm seeing is in where the DISTINCT operation is applied. Of those two plans, the faster plan has a HASH aggregate while the other does a completely useless...
"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
May 18, 2010 at 1:47 pm
I wouldn't be surprised if you see an operator in the execution plan called Key Lookup. If it's there, you're looking at an instance of a covering index and a...
"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
May 18, 2010 at 1:09 pm
Pretty much. There may be another way around, but I don't know it.
"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
May 18, 2010 at 11:05 am
Viewing 15 posts - 14,986 through 15,000 (of 22,219 total)