Viewing 15 posts - 13,561 through 13,575 (of 22,224 total)
It's just like running SQL Server on a virtual. Do you have enough resources? If so, yeah, it's fine. If not, no it's not. Actually, same thing as a physical...
"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 20, 2011 at 7:11 am
Yes, it's possible. It's actually the right way to go. If you remove all the objects from the filegroup you can drop the file and filegroup without affecting your database.
"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 20, 2011 at 7:02 am
I agree with Gail. Targeting functionality for a proc is better than trying to create a catch-all for any number of reasons.
"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 20, 2011 at 6:46 am
The problem is there aren't any hard & fast rules for data types & performance. Smaller is better, but if you have a number that won't fit in a tinyint...
"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 20, 2011 at 6:41 am
That's definitely odd behavior. Another thing to check, are there differences in the ANSI settings between the two procs? Other than that... I'm not sure.
"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 20, 2011 at 6:36 am
Ronnie Jones (1/20/2011)
So basically, it sounds like this process is manual meaning that I will have to look at each table to determine if I...
"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 20, 2011 at 5:49 am
SQL08Kid (1/18/2011)
Grant Fritchey (1/18/2011)
Has to be triggers or something going on behind the scenes.
Grant, what's the best way to see if anything is happening behind the scenes? This happens every...
"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 18, 2011 at 11:38 am
Has to be triggers or something going on behind the scenes.
"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 18, 2011 at 11:20 am
You'll get a plan for each query in the branch. I wouldn't think that would be the cause, but it might be related in some way.
"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 18, 2011 at 9:01 am
Steve Jones - SSC Editor (1/18/2011)
"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 18, 2011 at 8:22 am
That doesn't sound like an error. That sounds like a statement put the database in an offline condition.
"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 18, 2011 at 8:13 am
Lee Forst (1/18/2011)
"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 18, 2011 at 8:10 am
The thing is, your process is causing the blocking. I'd seek a solution by address the process. I think you're in a "Doctor, doctor, it hurts when I do this"...
"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 18, 2011 at 8:07 am
I'd refer to Itzik's book as well.
But, while you're waiting for it to arrive, there is some explanation here. Here's a bit more. None of this addresses it directly...
"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 18, 2011 at 7:57 am
Yeah, without a, pick your time period, 6 months/year/decade worth of transaction monitoring, there is no way to know what data was accessed.
If you're interested in what has been access...
"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 18, 2011 at 7:46 am
Viewing 15 posts - 13,561 through 13,575 (of 22,224 total)