Viewing 15 posts - 12,991 through 13,005 (of 22,224 total)
If you're getting an index scan, you should try to understand why. Is there something in the code, such as a function on the column, that is causing the scan?...
"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 21, 2011 at 5:53 am
I'm with Steve. I wouldn't advocate putting artificial data, especially financial data, into the database. It's just too likely to cause problems down the road.
"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 21, 2011 at 5:49 am
Just to state it as clearly as possible, nesting views is generally a bad idea.
Same goes for nesting functions.
The query optimizer is smart and effective, but it will throw up...
"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 21, 2011 at 5:46 am
If you've validated the data with SQL Data Compare, also validate the structure with SQL Compare. I'll bet other things are missing.
When you're not sure what a query is doing...
"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 21, 2011 at 5:43 am
All true but, the load placed on the TEMPDB by the consistency operations won't go away and could lead to to contention. If I was going to bother with offloading...
"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 18, 2011 at 8:12 pm
I agree with Pam, first place to look is the actual execution plans. Are they different, if so, what are the differences?
Another option to check, what are the ANSI connection...
"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 18, 2011 at 3:53 pm
[Jim].[dba].[Murphy] (3/18/2011)
Grant Fritchey (3/18/2011)
...you may want to take the consistency checks offline, perform them on a restored copy of the database or something.
I have to agree; also helps minimize 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
March 18, 2011 at 3:26 pm
Honestly, on most systems, on most databases, I just use the defaults. It's pretty rare that suggesting a marginal change in sampling rates will make that big a difference 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
March 18, 2011 at 3:17 pm
GilaMonster (3/18/2011)
Test the backupexec full with the log. I have 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
March 18, 2011 at 3:15 pm
Depending on the system, you may want to take the consistency checks offline, perform them on a restored copy of the database or something. I'd move that away from any...
"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 18, 2011 at 3:13 pm
Each of those INSERT statements is treated as a miniature transaction and the INSERT ... SELECT ... UNION is a giant transaction. That's probably where the differences lie.
"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 18, 2011 at 5:40 am
Chad Crawford (3/17/2011)
Wahoo! Just passed 70-454. I am now officially SQL 2008 DBD ITP. 😀 Yipee!
Congratulations, well done.
"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 17, 2011 at 2:49 pm
jason.spangler (3/17/2011)
I'm checking out the ad hoc workload option. Looks like it will help. We...
"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 17, 2011 at 10:44 am
Brandie Tarvin (3/17/2011)
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
March 17, 2011 at 9:00 am
It's an artifact I wouldn't sweat it. If you're getting the cache hit, you're good to go. You can also look at the execution plans to see if the 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
March 17, 2011 at 8:55 am
Viewing 15 posts - 12,991 through 13,005 (of 22,224 total)