Viewing 15 posts - 5,941 through 5,955 (of 22,219 total)
I agree about the filter on the database id... and disagree. As much as possible you should have it interrupt sooner rather than later to take advantage of the great...
"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 13, 2015 at 9:58 am
One point. I'm pretty sure duration in extended events is in microseconds. You might want to capture >2000000.
"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 11, 2015 at 10:12 am
I haven't set this up, but it shouldn't be at all hard. Documentation on the Task Scheduler is here. You'll want to use SQLCMD.EXE. You can just pass in a...
"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 11, 2015 at 9:10 am
There's no automated mechanism I'm aware of. You gather metrics about query behaviors and over time identify those that are causing you pain. Identify the fact that stats are causing...
"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 11, 2015 at 8:51 am
Absolutely no silver bullet. That basically looks OK. You may find that statistics updates weekly might be a little light. Depending on the size of your system and the load,...
"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 11, 2015 at 7:45 am
Thanks for posting back what you ultimately found. So sorry you're going through this nightmare. It can't be fun. Actual malicious actions against a server is not one I've personally...
"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 11, 2015 at 7:36 am
OK. Then, the other option may be true. You had a one or more very large transactions.
"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 11, 2015 at 7:29 am
No. Full backups don't control the logs, at all.
Simple recovery, the logs clear all committed transactions at checkpoint. Backups, full or differential (which are all you can do) don't affect...
"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 11, 2015 at 7:20 am
Real life badass, Dracula, Saruman, Christopher Lee is no more
"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 11, 2015 at 6:30 am
Yep. Itzik's books are absolutely the best.
"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 11, 2015 at 3:40 am
Capture the wait statistics on the job to see where it's slowing 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 10, 2015 at 6:53 pm
If the log has grown that's because there has been either some very big transactions, or there's a transaction that's open and not closed preventing the other transactions from clearing....
"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 10, 2015 at 6:51 pm
You could RAISERROR after the rollback is complete so that your alert fires.
"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 10, 2015 at 6:01 am
Just make sure you go to the execution plan to understand which of the indexes you have in place are being used and how they're being used. That can act...
"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 10, 2015 at 3:40 am
Usually follow the Cumulative Update path. When they come out, get them, put them on Dev, see what happens there and then slowly march them through the various environments prior...
"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 10, 2015 at 3:37 am
Viewing 15 posts - 5,941 through 5,955 (of 22,219 total)