Viewing 15 posts - 13,546 through 13,560 (of 22,219 total)
It's going to be difficult to put 2tb into 100gb, virtual or not.
"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 8:23 am
I actually just, just found another way you can do it. You can use extended events to capture all wait states on procedures as they occur. I don't have 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
January 20, 2011 at 8:22 am
That could work, but what other processes will be on the server? How much data do you have? I'm asking because i assume you're going virtual because you're going 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
January 20, 2011 at 8:14 am
sql_butterfly (1/20/2011)
Understood. It means as per thumb rule, the funtionality of a sproc should be as specific as possible and we should try to normalize the sproc as well.
Just so...
"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 8:05 am
GilaMonster (1/20/2011)
Grant Fritchey (1/20/2011)
My most recent post was about why do log files fill up. Believe me, other people have posted about it.
A topic I'm in the middle of writing...
"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:38 am
This is a somewhat big topic. There are probably 15-20 measures, minimum, that you ought to capture and interpret. You should also start capturing wait states to see what things...
"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:32 am
You basically can do two things, sample the waiting processes regularly during the day to see if you can catch a query waiting because of cxpacket or set up 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 20, 2011 at 7:29 am
Multi-statement user defined functions & table variables are estimated based on 1 row, so their "cost" estimates are extremely low when compared to regular & temp tables that have actual...
"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:27 am
Really hard to be sure without seeing the execution plan.
"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:21 am
It's pretty much whatever comes in front of you from day to day that you are either fascinated with, excited by or knowledgeable about. Preferably all three. You can't worry...
"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:15 am
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
Viewing 15 posts - 13,546 through 13,560 (of 22,219 total)