Viewing 15 posts - 13,501 through 13,515 (of 22,224 total)
Then I suspect either the text is very small or FTI is not being used. Again, the exec plan should tell the tale.
"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
January 25, 2011 at 12:28 pm
I'd check the execution plans. That's going to tell you what each operation is leading to. I would suspect that both LIKE and CONTAINS leads to a scan, but it...
"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
January 25, 2011 at 12:07 pm
SAnjy N (1/25/2011)
Thanks, I have only remote access. And I am not comfortable with Execution Plans. How to read them!
If you search on the web you can find 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
January 25, 2011 at 11:47 am
Is anything else running on the servers? If not, it's SQL Server that is probably causing the issue. Do you have monitoring set up so you can observe the behaviors...
"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
January 25, 2011 at 11:13 am
I'm not a fan of CASCADE. It takes away a lot of control and can lead to unintended consequences. I'd be careful about using it.
As far as the design goes,...
"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
January 25, 2011 at 11:08 am
Good points Gus. This is meant to be my introductory session on execution plans (it's going, more or less intact, into my SQL Rally all day session). Thanks. Great feedback.
"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
January 25, 2011 at 10:14 am
Not knowing how your backups are configured or running, it's hard to say. But it sounds like whatever process is running the backups either doesn't have that database included, or,...
"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
January 25, 2011 at 9:32 am
It's not something I've run into. Can you post the specific error message, if any?
Is there any chance a different process is also calling the log backup procedure?
"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
January 25, 2011 at 9:31 am
If you're not seeing CPU or Disk issues, I'd start looking for weird stuff. Do you have lots of connections unclosed? Are there uncommitted transactions? Stuff like that. Something that...
"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
January 25, 2011 at 9:28 am
Another possibility is differences in the physical boxes. We had a production box once that had slower CPU's the dev box. Made us crazy for a while til we noticed....
"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
January 25, 2011 at 9:26 am
scorpianprince (1/25/2011)
If huge transactions are happening and if the large insertions and deletions is a daily process then he don't have any other method.
If huge transactions are occurring daily that...
"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
January 25, 2011 at 9:22 am
Maybe use the rule of three's like you suggested for mine? I thought it was a good idea.
"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
January 25, 2011 at 8:52 am
Oooh, that sounds good. When are you putting that session on?
Seriously, thanks. That makes sense. I'll work that in with the edits I'm going to use from Roy's feedback.
"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
January 25, 2011 at 8:50 am
Me too. The last one works best. I think Resume still needs to be in the title.
"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
January 25, 2011 at 8:48 am
If it will help your tinkering (and you can write an article if you get done first), the approach I was going to take was to use PowerShell to do...
"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
January 25, 2011 at 8:46 am
Viewing 15 posts - 13,501 through 13,515 (of 22,224 total)