Viewing 15 posts - 9,886 through 9,900 (of 22,232 total)
No. CXPacket waits are an indication that you have a parallel process that is waiting. It can be an indication of high CPU use, but it's not the root cause....
"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
April 25, 2013 at 11:12 am
I would just add an ORDER BY clause to that TOP query. You can't guarantee the order of the data without 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
April 25, 2013 at 5:53 am
It's just a number used to perform & report on the math internal to the optimizer. It doesn't mean anything. However, it is represented as if it meant the amount...
"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
April 25, 2013 at 4:50 am
The best approach for tuning a query like this would be to start with the execution plan to understand how the optimizer is resolving it. That can help you apply...
"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
April 25, 2013 at 4:48 am
Any time you need to write a query, I usually take the approach of breaking it down into steps. For example, you need to see the average cost for each...
"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
April 25, 2013 at 4:44 am
If you run a query against sys.dm_exec_requests as I specified while the query is running, before it times out, you can see if it's getting blocked. That's what I would...
"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
April 24, 2013 at 10:13 am
It's one of the easiest upgrades I've ever done in SQL Server, but paranoia never hurts. I'd suggest running the upgrade advisor first.
"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
April 24, 2013 at 8:44 am
It sounds like a blocking issue. You can use the software suggested or just look at sys.dm_exec_requests to see if there are processes holding locks that will prevent your 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
April 24, 2013 at 8:42 am
You can even create filtered statistics in a similar fashion to help the optimizer.
"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
April 24, 2013 at 8:40 am
As long as they are calling procedures or creating parameterized queries, not really. It might tend to bloat the cache a little depending on how the calls are generated since...
"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
April 24, 2013 at 4:42 am
WayneS (4/18/2013)
Grant Fritchey (4/18/2013)
Late to the game, but well done Jason & Wayne.Thanks Grant.
BTW... are you the next MCM from the SSC group?
Ha! Doubtful. That requires actual brains & skills....
"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
April 21, 2013 at 4:47 am
dbursey (4/18/2013)
"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
April 21, 2013 at 4:44 am
Late to the game, but well done Jason & Wayne.
"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
April 18, 2013 at 6:08 am
You can query the execution plan from the plan cache. The execution plan will show how the query was resolved and will include if indexes were referenced at all 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
April 9, 2013 at 7:15 am
Yeah, it's a server level setting.
"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
April 9, 2013 at 7:07 am
Viewing 15 posts - 9,886 through 9,900 (of 22,232 total)