Heh... I know this is an old post but I've found out through experimentation since Nov 2017 that if you're using REORGANIZE for large tables, then you have much bigger things to worry about when it comes to log backup size, log shipping times, mirroring or always on log transfers. 😉 REORGANIZE on a 146GB table suffering only 12% Logical Fragmentation (well within supposed "Best Practices" of reorging between 10 and 30%) caused the log file to explode from 20GB to 227GB.
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