steve 96379 - Wednesday, April 4, 2018 7:07 AM
First, I really appreciate the fact that anyone would share information and try to make someone else's life a bit easier. You're definitely one of the "good guys". Thanks for sharing.
To Chris' point, though, the trouble is that you don't provide those warnings (the ones in your response above) anywhere in your write up or your code. You also don't warn that the creation of indexes is a wanton duplication of data and that on a huge but narrow table, SQL Server may include enough INCLUDEs to actually duplicate such a huge table. Neither do you include the notion of a correct FILL FACTOR, which is uber important to INSERTs, "expansive" (which are "expensive") updates, and the horrible page splitting problems that occur when you Reorg or (especially) Rebuild an index (especially with a 100% Fill Factor) during index maintenance.
When you post something like this, you have to remember that many people are not prone to reading the discussions that follow. Normally, they're desperate for a solution and such warnings and issues must be clearly identified right up front and short enough so that folks don't do the "TLDR:" thing.
--Jeff Moden
Change is inevitable... Change for the better is not.