I would run the stats rebuilds long before I ran the current industry standard for supposed "Best Practices" (Reorg between 5 and 30% logical fragmentation, REBUILD for more than 30%)... especially on any index where you don't know the exact INSERT/UPDATE pattern. Like I've said in the past, it's better to do no index maintenance than it is to do it wrong.
No... I am NOT saying that Ola's code is bad. In fact, I agree with Paul Randal in calling it the "Gold Standard" for index maintenance. The problem isn't with Ola's code... the problem is with how people use it. It's not actually an index "optimizer" (it's not capable of analyzing indexes and assigning the correct Fill Factor, for example). It's an excellent tool for doing index maintenance. If you use it following the industry wide supposed "Best Practices", then you're using Ola's code incorrectly (IMHO).
If your analysis for Fill Factor is based only on logical fragmentation, then you'll be doing that wrong, as well, because a whole lot of INSERT/UPDATE patterns are going to cause fragmentation even if you set the Fill Factor as low as 10%.
is pronounced "ree-bar
" and is a "Modenism
" for R
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.
"Change is inevitable... change for the better is not".
"Dear Lord... I'm a DBA so please give me patience because, if you give me strength, I'm going to need bail money too!"
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)