Viewing 15 posts - 12,736 through 12,750 (of 22,219 total)
Kenneth Wymore (4/15/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
April 15, 2011 at 9:14 am
Although, now that I'm thinking on it, you might want to take a look at Red Gate SQL Multi-Script[/url]. It might provide you with a bit more flexibility and power...
"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 15, 2011 at 6:08 am
I don't completely understand the situation, but if you need to run custom queries and respond to those results, yes, you probably need to build that yourself. But it won't...
"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 15, 2011 at 6:02 am
If you're doing the detach/attach, you might (might) be able to get away with it. Test it before-hand. You should test everything anyway.
"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 15, 2011 at 6:00 am
The database structure is not published. You can get some of it from the SDK documentation. I'd start there.
"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 15, 2011 at 5:47 am
Frankly? I've died and gone to heaven. I won the lottery. I asked the prettiest girl to the prom and she said yes. My code compiled the first time. 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
April 15, 2011 at 5:29 am
mtassin (4/14/2011)
Grant Fritchey (4/14/2011)
GilaMonster (4/14/2011)
Grant Fritchey (4/14/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
April 14, 2011 at 9:05 am
Stefan Krzywicki (4/14/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
April 14, 2011 at 8:23 am
I would look at sys.dm_os_wait_stats. It shows accumalative waits for SQL Server itself. That will give you an idea of what's causing problems on the machine without having to try...
"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 14, 2011 at 8:08 am
It depends on how you're making the call. If you want to run the PowerShell script directly from the 2005 server, you need to go and get Powershell installed there...
"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 14, 2011 at 7:46 am
I just want to reiterate and reinforce one statement. Hints are a last resort. You need to do every other method of tuning before you get to hints. Not only...
"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 14, 2011 at 7:42 am
No way I would run any kind of load generation tool against a live production server, regardless of circumstance on the monitoring.
Have you looked at wait stats? You can start...
"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 14, 2011 at 7:24 am
Just remember that auto-growth is a safety valve, not a management plan. You should set the database to be bigger than it needs to be and then monitor the space...
"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 14, 2011 at 7:23 am
It sure sounds like contention. Next time it's running slow, start with sys.dm_exec_requests and see what the process is waiting on and if it's blocked. You can proceed from there...
"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 14, 2011 at 7:21 am
I wouldn't go down to a single file or filegroup on the new system. 5 seems like overkill, but I'd still have at least 2.
"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 14, 2011 at 7:19 am
Viewing 15 posts - 12,736 through 12,750 (of 22,219 total)