Viewing 15 posts - 10,726 through 10,740 (of 22,219 total)
Duplicate question. Please direct all answers to this post.
Please don't cross-post in the different discussion groups. Most of them are read by the same people. It just leads to confusion.
"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
June 19, 2012 at 3:38 pm
True. If the queries age out of cache you're in trouble. But, you'll get the most active queries immediately and you can capture more by rerunning the query against 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
June 19, 2012 at 3:16 pm
All the hints included in a query are stored with the execution plan, so you could query the plans, using XML, to pull the information out of the DMVs. 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
June 19, 2012 at 3:07 pm
It's xml_deadlock_report event, which is the deadlock graph.
"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
June 19, 2012 at 11:08 am
Hmmm... A couple of points. I encrypted a proc and made a deadlock occur with it. I did get back the statement information as part of the XML deadlock graph...
"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
June 19, 2012 at 9:04 am
Oh, you're pulling it from the extended event data. That's great. Well done. Still, doesn't change things. I'm not sure how encryption affects it. I'm going to try to set...
"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
June 19, 2012 at 8:34 am
Ah, you know, I'm not sure. It might.
You're using traceflag 1222 to capture 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
June 19, 2012 at 8:17 am
Try using the OBJECT_ID function with the database and object ID that are part of the input buffer. That should narrow it down.
"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
June 19, 2012 at 5:38 am
GilaMonster (6/19/2012)
Brandie Tarvin (6/19/2012)
"Surface"? Really?What kind of marketing department names a tablet with such a mundane moniker?
Surface was previously the name of their table computer (touch screen, about the size...
"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
June 19, 2012 at 5:35 am
george sibbald (6/19/2012)
based on all the tables being about that size, I agree with you, you'll be glad to hear.not my post btw 🙂
Ooops. Just saw the question. Didn't look...
"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
June 19, 2012 at 5:28 am
NO! Don't use readuncommitted or nolock. Those lead to differences in the data returned by the query[/url] and are generally not a good solution.
Instead, first, tune the query. All those...
"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
June 19, 2012 at 5:24 am
george sibbald (6/19/2012)
Grant Fritchey (6/18/2012)
I doubt you're seeing major performance hits from the fragmentation, .why do you say that grant?
Just because, at least from what you've posted, the tables are...
"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
June 19, 2012 at 5:03 am
Suresh B. (6/19/2012)
how to ensure that correct execution plan is created and used every time it executes ?
Add OPTION (HASH JOIN) at the end of the query.
how to check 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
June 19, 2012 at 4:51 am
WayneS (6/18/2012)
Me, your humble dba, from out of the blue, happened...
"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
June 19, 2012 at 3:56 am
I doubt you're seeing major performance hits from the fragmentation, but I'd go ahead and defragment anyway. You're only storing, on average, 1.6 pages per extent, so you'll get some...
"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
June 18, 2012 at 4:05 pm
Viewing 15 posts - 10,726 through 10,740 (of 22,219 total)