Viewing 15 posts - 10,351 through 10,365 (of 22,224 total)
I'd love to hear the reasoning behind that.
"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 17, 2012 at 8:23 am
Problem is, if another insert occurs on the master table before you get to your detail table, IDENT_CURRENT will not return the one you want. In order to 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
October 17, 2012 at 8:21 am
The two books below in my signature can help with query tuning. I also wrote part of an introductory book called Begginning SQL Server 2012 Administration. After that, all 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 17, 2012 at 8:15 am
The only problem with RDP is that if you have 3rd party tools to help you with your work, and you have individualized settings on those tools, RDP sessions require...
"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 17, 2012 at 8:11 am
You can get aggregate information about queries from the dynamic management objects (DMO), specifically by querying sys.dm_exec_query_stats. But, that assumes that the query is still in cache. If it's aged...
"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 17, 2012 at 8:10 am
At one point, when I had too much to support, I had 2000, 2005, 2008, 2008R2 and a beta of 2012 all running on the same machine (with two different...
"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 17, 2012 at 8:08 am
It is hard to figure out how to deal with wildly deviant feedback. "Best session of the day" and "Whiny dick" were two of the feedback I got in OKC...
"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 16, 2012 at 5:31 am
I really enjoyed that trip, although I came home utterly exhausted at the end of it. Worst thing was trying to remember what I had said or not said during...
"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 16, 2012 at 4:25 am
ScottPletcher (10/11/2012)
Grant Fritchey (10/11/2012)
ScottPletcher (10/11/2012)
Grant Fritchey (10/11/2012)
As an aside, the CHAR(2) would be a really poor choice for the first column in a compound key. You'd want to use either...
"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 11, 2012 at 12:34 pm
ScottPletcher (10/11/2012)
Grant Fritchey (10/11/2012)
As an aside, the CHAR(2) would be a really poor choice for the first column in a compound key. You'd want to use either the INT or...
"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 11, 2012 at 12:07 pm
I'd be nervous about creating that many indexes, especially if you're only saving a few pages read from memory. If the query was called thousands of times a minute, heck...
"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 11, 2012 at 6:01 am
First things first, estimated costs are not measures that you can compare between queries. They are too subject to odd variability, so don't look at cost estimates within execution plans...
"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 11, 2012 at 5:08 am
PiMané (10/11/2012)
I've already discussed this point but if you can enlighten me a little more I'd be grateful 🙂
Suppose I have an index I1...
"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 11, 2012 at 4:09 am
PiMané (10/11/2012)
ScottPletcher (10/10/2012)
A three-column is not slower to do lookup on if that's what you (almost) always specify...
"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 11, 2012 at 4:03 am
PiMané (10/10/2012)
Grant Fritchey (10/10/2012)
"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 11, 2012 at 3:57 am
Viewing 15 posts - 10,351 through 10,365 (of 22,224 total)