Viewing 15 posts - 17,791 through 17,805 (of 22,219 total)
The one that comes built in with SQL Server. It's not great, at all, but it does the basics reasonably well. If you have a full Office license there's also...
"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 7, 2009 at 5:53 am
Can't you use WITH REPLACE just like you would with a regular full backup restore when the tail hasn't been backed up?
"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 7, 2009 at 5:40 am
Me too. This place is excellent. Thanks Steve.
"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 7, 2009 at 5:36 am
Jeffrey Williams (4/6/2009)
I use powershell scripts 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
April 7, 2009 at 5:23 am
We've started using PowerShell more and more, but not so much for monitoring since we use Operations Manager for that. We've mainly been using it as a means for cleaning...
"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 6, 2009 at 7:03 pm
It is possible that checking the queries and getting a good index in place may help as well. I'm personally not a fan of the DTA, but it can help....
"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 6, 2009 at 6:59 pm
First, turn off 1204 when you're collecting the info with 1222. It'll cut down on the noise and make it a bit easier to read.
Second. You're getting lock escalation as...
"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 6, 2009 at 6:36 pm
All three queries are going after sgDataOPERATIONS. Is there a read statement prior to the delete statements that would cause lock escalation? What do the execution plans look like on...
"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 6, 2009 at 1:31 pm
1204 puts out a hard to use deadlock graph. If you can, can you recapture it using traceflag 1222? That one is much cleaner and easier to read.
"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 6, 2009 at 1:20 pm
Check the actual execution plan. In the properties of the various processes it will show you if you're using parallelism and how many threads were used by the process.
"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 6, 2009 at 1:00 pm
Excellent. Glad you tracked it down. Thanks for posting the solution here.
"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 6, 2009 at 11:33 am
I'm really against a black list. I'm far too likely to end up on it one day. Plust I'm probably not going to consult it until I've already stepped into...
"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 6, 2009 at 11:32 am
Wilfred van Dijk (4/6/2009)
Yes, I know the meaning of this error, but why is the same statement giving this error in a Job and not in a query window???
Assuming 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
April 6, 2009 at 8:31 am
Best wishes Roy.
"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 6, 2009 at 7:36 am
There's no 100% sure way to verify that things are not used in your database. As others have outlined, it's possible to see whether or not things have been accessed...
"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 6, 2009 at 7:29 am
Viewing 15 posts - 17,791 through 17,805 (of 22,219 total)