Viewing 15 posts - 14,536 through 14,550 (of 22,219 total)
In addition to Gail's list:
Different Parameters
"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
August 5, 2010 at 6:16 am
Depending on what was deadlocked and how it resolves, you may not get this information. Usually, when we have a system that is experiencing deadlocks, we put a server-side trace...
"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
August 5, 2010 at 6:08 am
If you want to literally simulate the entire user experience, with waits and everything, I'd suggest taking a look at Quest's Benchmark Factory. We've been able to use it 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
August 4, 2010 at 1:15 pm
And there's always the weird stuff. We had a developer accidently drop his access to one stored procedure because he wanted to test security so he revoked his privs, but...
"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
August 4, 2010 at 12:59 pm
Yeah, true, it doesn't put in pauses. But I don't think that's the worry in this case, unless I'm wrong. Wouldn't be the first time... this hour.
"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
August 4, 2010 at 12:49 pm
Yes and no. It kind of depends on how big the machine doing the playback is since it will need to thread the calls and may not be able 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
August 4, 2010 at 12:11 pm
Yeah, I'd go with Profiler as well. The only issue you might run into with that approach is if you have ad hoc SQL that is using deprecated functionality, like...
"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
August 4, 2010 at 11:30 am
Brandie is 100% correct. You'll need to reinstall SQL Server.
"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
August 4, 2010 at 8:57 am
Simply moving them to a seperate file will get you some, very moderate, performance gains, but moving them to their own disk will help a ton. But, it's still best...
"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
August 4, 2010 at 8:56 am
One of these must be returning zero:
SUM(TotalMaterialValue) / SUM(TotalQuantityMade) AS AverageMaterialCost,
SUM(TotalLabourValue) / SUM(TotalQuantityMade) AS AverageLabourCost,
SUM(TotalOverheadValue) / SUM(TotalQuantityMade) AS AverageOverheadCost,
SUM(TotalTotalValue) / SUM(TotalQuantityMade) AS AverageTotalCost,
SUM(TotalTimeBookedMinutes) / SUM(TotalQuantityMade) AS AverageTimeInMinutes,
SUM(TotalTimeBookedHours) / SUM(TotalQuantityMade) 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
August 4, 2010 at 8:47 am
You can use a variable on an insert, but there has to be a column to insert it into. You can't just throw it in as a placeholder.
And yes, it's...
"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
August 4, 2010 at 8:30 am
I doubt there's an article out there comparing the two because they aren't really something you compare. Here's the BOL entry for max degree of parallelism and degree of parallelism....
"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
August 4, 2010 at 8:28 am
Because you're working with 2000, this will be harder, but what you need to do is analyze the wait states and queues to figure out what you're slowing down 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
August 4, 2010 at 8:24 am
Brandie Tarvin (8/4/2010)
Grant Fritchey (8/4/2010)
"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
August 4, 2010 at 8:11 am
Complete agreement with Gail. Rather than knock yourself about moving the index locations (you just have to recreate the indexes and reference the new file or filegroups using the 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
August 4, 2010 at 6:40 am
Viewing 15 posts - 14,536 through 14,550 (of 22,219 total)