Viewing 15 posts - 7,966 through 7,980 (of 22,224 total)
With log buffer waits, it's hitting conflicts with other processes in and around the log. It might just be slow.
"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 16, 2014 at 3:24 pm
Are there waits associated with the process? It's likely that it's just taking a long time or that it's blocked.
"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 16, 2014 at 1:05 pm
In general, I'd go with the first query. I think the optimizer will figure it out in most circumstances, but that assumes you have an enforced referential constraint 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
June 16, 2014 at 1:04 pm
Based on the amount of information you have shown, it could be SQL Server. The reads are quite a bit higher I production. I'd suggest getting the execution plan from...
"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 16, 2014 at 1:01 pm
And are there differential backups? If so, this stuff could be breaking your backup chain, which could lead to all sorts of fun when you try to recover.
"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 16, 2014 at 8:30 am
There are a number of tools you can set up to track changes to the system. If you want to track individual queries you can use extended events or trace....
"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 16, 2014 at 6:39 am
Kind of a shame to not let others see the question or provide a solution. Others could benefit from whatever issue you hit.
"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 16, 2014 at 4:39 am
SQL Server 2008 has a system_health extended event session. I'm pretty sure it's capturing information from your deadlock called a deadlock graph. You'll need to query the files to get...
"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 15, 2014 at 4:09 am
Koen Verbeeck (6/14/2014)
Grant Fritchey (6/14/2014)
Koen Verbeeck (6/14/2014)
Ah, the world cup......
Spoilsport.
England plays today!
WHOOOOP!!!
I bet they are going to lose. Hard. 😀
And they did. Well, not that hard, but a loss 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
June 15, 2014 at 4:05 am
Koen Verbeeck (6/14/2014)
Ah, the world cup...
Spoilsport.
England plays today!
WHOOOOP!!!
"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 14, 2014 at 5:14 am
Both the server-side trace and extended events can be set up to run from a SQL Agent job so that they start at a particular time. Both can also 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
June 14, 2014 at 4:10 am
ramana3327 (6/13/2014)
I am running in dev box only. So stats were not very up to date. Usually to test the changes do we need to run the stats before...
"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 14, 2014 at 4:08 am
I'd ask for a demonstration of a point in time restore. If it can restore to 3:57PM yesterday, accurately, without a corrupt database, go with it. I've seen SAN snapshot...
"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 14, 2014 at 4:05 am
I agree with Howard. I have seen some interesting improvements in performance because of the new cardinality estimation across quite a few queries, including some I wouldn't have expected to...
"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 14, 2014 at 4:01 am
Did you read the post I linked to? You need to have log backups enabled.
"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 14, 2014 at 3:57 am
Viewing 15 posts - 7,966 through 7,980 (of 22,224 total)