Viewing 15 posts - 6,616 through 6,630 (of 22,219 total)
UPDLOCK is telling the server that you want to take out a lock on the table as if you were getting ready to update it. Then, the HOLDLOCK hint tells...
"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
March 10, 2015 at 6:54 am
rodjkidd (3/10/2015)
ChrisM@Work (3/10/2015)
rodjkidd (3/10/2015)
Eirikur Eiriksson (3/10/2015)
rodjkidd (3/9/2015)
Eirikur Eiriksson (3/9/2015)
Grant Fritchey (3/9/2015)
And, I got to meet Gianluca and Eirikur for the very first time. Total...
"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
March 10, 2015 at 5:44 am
Brandie Tarvin (3/9/2015)
Jack Corbett (3/9/2015)
"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
March 9, 2015 at 12:31 pm
Bouke Bruinsma (3/9/2015)
Grant Fritchey (3/9/2015)
ChrisM@Work (3/9/2015)
The optimiser has difficulty with more than seven or eight tables in the FROM list regardless of how they are joined. More than that 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
March 9, 2015 at 9:44 am
Great seeing everyone this week at SQLBits.
And, I got to meet Gianluca and Eirikur for the very first time. Total pleasure gentlemen. By the way, Gianluca is a giant.
"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
March 9, 2015 at 8:22 am
It's all about the log backup and the recovery model. You can read about it here[/url].
"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
March 9, 2015 at 7:48 am
I don't think it would cause issues, but I'm not clear on what problem it solves.
"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
March 9, 2015 at 7:01 am
Grace09 (3/8/2015)
SELECT DISTINCT .[ID], .[ParentID]
FROM [Items]
WHERE LOWER(.[Name]) = 'Test'
execution plan is...
"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
March 9, 2015 at 7:01 am
t.mounika01 (3/6/2015)
"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
March 9, 2015 at 6:58 am
It sounds like a blocking or resource contention issue. Let's assume that your queries are tuned, but they suddenly start timing out. It's likely that there's one resource of 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
March 9, 2015 at 6:53 am
What is the cost of the query as it currently exists?
Setting your threshold to 5 might work, but only if the cost of that query is over 5. If it's...
"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
March 9, 2015 at 6:46 am
ChrisM@Work (3/9/2015)
The optimiser has difficulty with more than seven or eight tables in the FROM list regardless of how they are joined. More than that and you are very likely...
"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
March 9, 2015 at 6:44 am
Most tables in most systems (and by most, 99% plus a few extra digits) should have a clustered index. It doesn't have to be unique as defined, although it's better...
"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
March 9, 2015 at 6:40 am
Assuming no data manipulation, you might also be able to use a scalar function. Due caution, testing, your mileage may vary, etc. But, it'll make the code a lot easier...
"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
March 9, 2015 at 6:37 am
Bouke Bruinsma (3/9/2015)
You might try creating a few views to break up the query.
I myself an against views altogether. The current view is part of an application. I can change...
"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
March 9, 2015 at 6:34 am
Viewing 15 posts - 6,616 through 6,630 (of 22,219 total)