I just checked my list of “miscellaneous” posts and see that it has been quite a while since I blogged a rant. I think it is time for another installment in the Little Things Doth Crabby Make series. Unlike usual, however, this time it isn’t I which the little thing hath crabby made. No, it’s got to be Microsoft on the crabby end—although I contend it is no “little thing” in this case.
According to Ed Bott’s blog post on the matter, Microsoft has fingered SQL Server as the culprit behind a recent service outage on MSDN and TechNet. What’s that adage? Eating one’s own dog-food? Anyway, the supposed SQL Server problem was database fragmentation. Huh? The tonic? According to Ed:
I’m told that Microsoft engineers are now monitoring the status of this database every 30 minutes and plan to rebuild the indexes every evening to avoid a recurrence of the problem.
How fun…playing with indexes—nightly!
And, yes, the title was a come-on. Oracle Database 11g fragmentation? Puh-leeeeze.
Kevin Closson's Blog: Platforms, Databases and Storage 
Oh yeah!: rebuilding indexes is very much still a large part of the life of a MSSQL dba.
Unreal. But quite true.
Worse: many third party application providers will NOT support a site where the dbas don’t rebuild the indexes daily.
Even though avoiding the problem in the first place is relatively simple from 2005 onward.
It’s not just Oracle that has myths…
Other sources speak about other (hardware ressources) reasons. I don’t think we should jump the gun so fast.
Bernd
There is this
http://sqlcat.com/faq/archive/2009/05/08/windows2008-r2-beta-download-runs-smoothly-now.aspx