Viewing 15 posts - 11,296 through 11,310 (of 22,219 total)
Parameter values are not stored. If a procedure has 4 parameters, then a plan will be created that has spaces for 4 parameters. Sniffing will ensure that the plan stored...
"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
February 8, 2012 at 6:01 am
Lynn Pettis (2/7/2012)
Kassondra gave birth to a healthy baby boy yesterday in Germany. Grayson Matthew was born 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
February 7, 2012 at 2:41 pm
mtassin (2/7/2012)
I don't see different query plans with 4136 on or off, I see vastly different performance with respect to response times. So much so that I would 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
February 7, 2012 at 11:15 am
mtassin (2/7/2012)
GilaMonster (2/7/2012)
I will admit, recompile would not be my first or even second option for dealing with parameter sniffing.
Personally dealing with parameter sniffing I prefer Traceflag 4136. 🙂
Really?
Wow.
I...
"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
February 7, 2012 at 10:18 am
I have not seen it, but the first two look like system generated statistics. That's nothing to sweat since they're going to be completely rebuilt anyway since statistics generated in...
"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
February 7, 2012 at 8:51 am
If it's scanning the index, it can mean you're returning so much data that it has not choice but to scan. Or, it could mean that the index isn't very...
"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
February 7, 2012 at 6:49 am
erikpoker (2/7/2012)
For simplicity, lets say i only grouped by two columns in the query. Account_FK and...
"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
February 7, 2012 at 6:46 am
Sorry, I read through your explanation of why you have to use a DISTINCT several times and I'm not getting it. Probably more than usually thick this morning. Sorry.
Could 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
February 7, 2012 at 6:02 am
GROUP BY and DISTINCT are both aggregate operations, so you might not have saved anything there.
In general, check the SELECT properties. If you see a timeout as the reason...
"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
February 7, 2012 at 5:58 am
Also use STATISTICS IO and compare the number of reads and writes. Do that in addition to measuring time. Both are applicable.
"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
February 7, 2012 at 5:48 am
It can affect the other processes, yes. No process you run is free of cost. Doing a scanned update of statistics is fairly low cost, and usually you can run...
"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
February 7, 2012 at 5:45 am
For quick information on what's running slow, use sys.dm_exec_query_stats to pull out the most frequently called queries or the longest running queries. From there though, you need to know 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
February 7, 2012 at 5:40 am
Nope, not a single issue at all. Great way to do the upgrade. I've done... oh, a whole bunch that way.
However, you should run the Upgrade Advisor first because 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
February 7, 2012 at 5:38 am
The fact that you need a DISTINCT operation in there suggests you might have a structural or data problem you need to concentrate on first.
Also, why are you returning 50000...
"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
February 7, 2012 at 5:33 am
Yeah, totally different. When I've run into that one it's usually been a configuration issue. Either I'm not running the right SP on the server, or the developers are running...
"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
February 6, 2012 at 12:37 pm
Viewing 15 posts - 11,296 through 11,310 (of 22,219 total)