I absolutely agree with Gail on ignoring the "fragmentation" you're seeing. Without writing a whole article about it here (Brent Ozar has several, which is where I got the idea from), I'll summarize by saying that stopped all index maintenance on my production boxes way back on the 17th of January, 2016 (almost a year and a half ago). It was odd to watch performance actually improve over the first 3 months and there isn't a much wasted space due to page splits as you would think... it eventually get's used.
Ironically and in direct contrast to the above, we used to get a truly significant amount of blocking on Monday mornings (the index maintenance occurs on Sundays) and all of that stopped when I stopped rebuilding indexes.
To emphasize, performance is in the code, having the correct indexes, and being religious about keeping statistics up to date. Fragmentation rarely comes into play on GUI related queries and, with today's SANs and the extremely random effects of having sometimes hundreds of users hitting the data, usually causes no ill effects on batch code either.
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)