I know about the online and logging aspects.
My question is which should be done before the other -- rebuild first
or reorganize first??
The databases involved are all small -- 4 GB or less...and we do have
downtime windows, plus enough space for the logs etc.
Presently we do a weekly maintenance: 1) check db integrity; 2)
rebuild indexes; 3) clean up history.
I'm just wondering how often to do a reorganize or whether to do
rebuild less often and to reorganize every week instead (means also
adding in the statistics task too).
Thank you, Tom
On Aug 22, 2:01 pm, Ekrem Önsoy compecta.com> wrote:
> Rebuilding Indexes online is a SQL Server (2005\2008) Enterprise Edition
> feature.
>
> You don't have to rebuild or reorganize your indexes unless necessary. These
> operations can be costly in resect of your databases and workload. Also,
> these are logged operations. Which means, they are going to be recorded in
> your Transaction Log file which means IO work. However, if you set your
> database's recovery model to Bulk Logged than this burden will not be that
> scary. I don't know about your databases nor your indexes, however you want
> you keep these cautions in your mind.
>
> Also, offline index rebuilding will lock your related tables and they'll not
> be available to your users (to modify data) during this operation.
>
> I suggest you to read (even a little bit) about these operations before
> deploying them. So, you'll have a better understanding about their
> effects\side effects on your system. You can find good technical info in
> Books Online. (
http://msdn.microsoft.com/en-us/library/bb418498.aspx)
>
> --
> Ekrem Önsoy
>
> "tlyczko"
gmail.com> wrote in message
>
> news:fda0edf7-48e4-4372-807f-1750cdbbd797@a1g2000hsb.googlegroups.com...
>