Index rebuilds won't make a database go offline unless the logfile explodes large enough to fill the disk it's on.
Index rebuilds will make the table data unavailable (which will obviously affect performance1) if you don't do them in an ONLINE fashion but there are some pretty cool workarounds for that (and you should look for workarounds because ONLINE rebuilds suck as almost as bad as REORGANIZE).
IMHO, never use ONLINE or REORGANIZE unless someone holds a gun to your head or you've one something really stupid with the LOB datatypes. If you've got VARCHAR(MAX) in your tables an you've not forced the large datatypes to go out of row, you've been a bit ignorant (I know I was) but REORGANIZE isn't going to be your savior even then.
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.
"If you think its expensive to hire a professional to do the job, wait until you hire an amateur."--Red Adair
"Change is inevitable... change for the better is not."
When you put the right degree of spin on it, the number 3|8
is also a glyph that describes the nature of a DBAs job. 😉
How to post code problems
Create a Tally Function (fnTally)