Viewing 15 posts - 13,021 through 13,035 (of 22,224 total)
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
Reorg is specifically for indexes that are only lightly fragmented as a way to give them an augmented performance metric at very low cost. You're looking 90% fragmentation. you need...
"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:42 am
GilaMonster (3/15/2011)
WayneS (3/15/2011)
So Gail - how did your presentation go? I'm sorry that I couldn't see it.
Awesome. Great fun. Timing went perfectly too (for once)
Trying to figure if I managed...
"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:21 am
I'd say Nivek summed it up fairly well 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
March 15, 2011 at 11:47 am
Even on a reporting server you might want to consider changing the defaul threshold for parallelism to a higher number. I wouldn't go as high as on an OLTP system,...
"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 15, 2011 at 9:55 am
In the glance through, nothing leaped to my eye except the cursors as well. But I'm in agreement with Steve.
"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 15, 2011 at 9:54 am
First thing that jumped out at me: dbo.AncestorsAndDescendantsOfSubAccount(@subacct) Family
Is that a multi-statement user defined function? If so, that's where I'd start. Eliminate that.
Without an execution plan, it's hard to know...
"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 15, 2011 at 9:48 am
Sorry, just trying to understand. I saw remote and local and inferred. Remember, I'm not there. I'm just going off what I'm told.
When you say remote, do you mean remote...
"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 15, 2011 at 8:37 am
that makes sense. I've heard of getting dupes in identity, but i think it was a one-off bug or something. Certainly nothing standard.
"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 15, 2011 at 8:29 am
Viewing 15 posts - 13,021 through 13,035 (of 22,224 total)