Viewing 15 posts - 13,021 through 13,035 (of 22,232 total)
Joe Korn (3/16/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
March 16, 2011 at 6:07 pm
You simply reorganize the clustered index, nothing happens to the nonclustered index. If you rebuild the clustered index, the nonclustered index is automatically rebuilt as well.
"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
March 16, 2011 at 6:06 pm
It looks like the Stream Aggregate is getting called in a loop. If you look at the actual output from it, it has 83 rows. The table spool is executed...
"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
March 16, 2011 at 6:04 pm
Jeff Moden (3/16/2011)
Craig Farrell (3/16/2011)
GilaMonster (3/16/2011)
I object, I'm a model of good behaviourwell, compared to others on that list anyway...
Isn't that like saying you're a 'nice' barbarian because you 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
March 16, 2011 at 5:51 pm
Yes and no. DBCC is subject to contention issues the same as almost any other process. Assuming no connections and no activity, yes, I'd expect it to run more 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
March 16, 2011 at 4:39 pm
BTW, Gail lives in South Africa which is about 6 hours ahead of us. It's near midnight her time. She's up this late sometimes, but sometimes not. 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
March 16, 2011 at 4:08 pm
Are you looking for sys.dm_db_index_physical_stats?
A query would look something like this:
SELECT * FROM sys.dm_db_index_physical_stats(DB_ID('AdventureWorks2008R2'),object_id('person.address'),NULL,NULL,'sampled') AS ddips
"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
March 16, 2011 at 4:07 pm
No, you really can't do that. You're going to have to get to that user and train them or get ahold of their code and clean it up. Either 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
March 16, 2011 at 4:03 pm
Did a few tests and this seemed to work just fine:
EXEC sys.sp_renamedb @dbname = [MyDB ], -- sysname
@newname = [MyDB2] -- sysname
;
EXEC sys.sp_renamedb @dbname = [MyDB2],...
"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
March 16, 2011 at 4:01 pm
GSquared (3/16/2011)
GilaMonster (3/16/2011)
CirquedeSQLeil (3/16/2011)
GilaMonster (3/15/2011)
WayneS (3/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
March 16, 2011 at 3:53 pm
Brandie Tarvin (3/16/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
March 16, 2011 at 12:50 pm
Unless you want to look at SQL Server 2008 R2 multi-server management, you're just going to have to set up a lot of manual processes out to multple servers. No...
"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
March 16, 2011 at 6:42 am
Here's some info on the default 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
March 16, 2011 at 6:37 am
It sounds like you're getting spikes on usage. That can be normal. A particularly nasty query used the CPU a lot and then cleared. The problem with setting a threshold...
"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
March 16, 2011 at 5:46 am
Another way that sometimes works is to eliminate the OR by rewriting the query to use UNION ALL and then putting each side of the OR clause on either side...
"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
March 16, 2011 at 5:44 am
Viewing 15 posts - 13,021 through 13,035 (of 22,232 total)