Viewing 15 posts - 17,461 through 17,475 (of 22,226 total)
That's a huge topic. If you're expected to deliver all this stuff NOW and you don't know how, you really are over your head. However, this is a high level...
"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
May 14, 2009 at 6:56 am
It really depends on the query being run. Most of the time, a JOIN is the preferred methodology. However, there are queries where the IN statement will work just 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
May 14, 2009 at 6:54 am
The the vast and overwhelming majority of systems, you should do both.
The algorythm that decides whether or not to update statistics is pretty good, but it's not perfect. Most people...
"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
May 14, 2009 at 6:51 am
Sounds like a good problem to have.
Buy a big box, with lots of memory... Sorry, but no one can help much past that without a lot more definition of 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
May 14, 2009 at 6:42 am
I think this one will require application of the Mk1 Eyeball and the 19xx release of Brain.
There are too many variables possible for a script to automate the process. 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
May 14, 2009 at 6:41 am
I agree, it depends.
A large majority of our applications have transaction control from the code, not within the procedures, so while we use TRY/CATCH error handling, we don't have a...
"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
May 14, 2009 at 6:35 am
No index is automatically created when you create foreign keys.
"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
May 14, 2009 at 6:23 am
And the size of the databases in production keep growing so you have to have 5-10 times as much space in dev since you have multiple copies of everything. Then...
"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
May 13, 2009 at 5:37 pm
Ah, I didn't see the bit about the rowmodctr. And I forgot all about it. However, since it only takes a single modification to make a statistic available for update......
"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
May 13, 2009 at 12:06 pm
Hmmm... It's my understanding that sp_updatestats does nothing more than cursor through all the tables in the system running UPDATE STATISTICS against them. I just rechecked that in the Books...
"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
May 13, 2009 at 10:40 am
I've been losing this fight for years. Just recently we had the financial people get involved. When they found out that the developers couldn't guarantee consistent tests since the production...
"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
May 13, 2009 at 9:56 am
If you're running it in conjunction, run it before and then run the new script.
"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
May 13, 2009 at 8:59 am
No, running updatestats updates any and all statistics on the target you select. So if you need updated non-index statistics, great, but you're still going to get a sampled update...
"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
May 13, 2009 at 6:23 am
Off the top of my head, I'm not sure. I don't think they would be affected negatively by running after the index rebuild.
"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
May 13, 2009 at 5:29 am
If you do a full index rebuild, it has sampled all the data, just like an update statistics with a full scan. If you then run the sampled statistics update,...
"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
May 12, 2009 at 6:32 pm
Viewing 15 posts - 17,461 through 17,475 (of 22,226 total)