Viewing 15 posts - 12,046 through 12,060 (of 22,224 total)
If you recreate it with a smaller size, I think that's what you're looking for.
"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 18, 2011 at 5:31 am
DISTINCT is an aggregation. Will it always increase execution time? No, but it frequently does. It's usually put in as a crutch because someone doesn't know how to properly write...
"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 18, 2011 at 5:15 am
Just can't tell you a thing beyond what Jeff has suggested without seeing the execution plan.
Numeric 19,0? Not an integer or a bigint? Is that data type the same 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 18, 2011 at 5:11 am
It sounds like you've hit a regression. These are edge cases where a query that, honestly, should have run slow in 2000, didn't. But now, it does. Every edge case...
"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 18, 2011 at 5:08 am
The conversation bounced around a bit, but it sounds like you could use three things. First, and most importantly, a well documented development & deployment method that you can enforce...
"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 18, 2011 at 5:02 am
More than likely it filters the tables and then combines the results. But, you should look at the execution plan. That will tell you precisely what happens.
"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 18, 2011 at 4:52 am
This is how Microsoft suggests you get that job 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
August 18, 2011 at 4:50 am
There are several different tools from various vendors that advertise this feature, but frankly, they're either weak or dangerous. I wouldn't recommend using any of them at this point in...
"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 17, 2011 at 12:14 pm
Those are ANSI standard settings. I'd say it's a good practice to have them on, but I don't think you'll see performance and indexing changes from having them enabled.
What performance...
"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 17, 2011 at 12:02 pm
Perry Whittle (8/17/2011)
Steve Jones - SSC Editor (8/16/2011)
Best advice, use backup compression first. If you have Enterprise Edition, you can use that
not available in SQL Server 2005, you will 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
August 17, 2011 at 11:54 am
The end of the backup process marks transactions as rollforward or rollback depending on if they're completed or not when the backup finishes. So you can get both situations, 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
August 17, 2011 at 8:58 am
The size of the transaction log is usually reflective of the size of the transactions. Have you tried monitoring the freespace in the tran log during the index rebuild. 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
August 17, 2011 at 8:56 am
A server side trace capturing a reasonable number of columns and events (depending on the events, statement level execs for example would be bad) will not be noticeable on most...
"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 17, 2011 at 7:41 am
Or Team Foundation Services, or Vault, or SVN... anything but VSS.
"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 17, 2011 at 7:04 am
I'd suggest doing a search online for Bill of Materials database designs. There are a bunch out there because it's a common problem. Use one of them as the basis...
"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 17, 2011 at 5:52 am
Viewing 15 posts - 12,046 through 12,060 (of 22,224 total)