Comprehensive as the "Recommendations" are, in small shops they become more of an irritation because there's no "Fix It/Recommended Fix Action" provision. In "no-DBA" shops it's simply saying "it's broke - fix it... good luck!".
When it comes to items such as Index Fragmentation I could persuade the powers that be to invest in I***a's Defrag Manager... Bet you could make a Rolls Royce version of that one... 8) According to a widely available Index Analysis script, I have 75 indexes per night that need some TLC. With reindex operations generating 2gigs of logs on 15 of those per night, on a mere 6gig db, you could say "Help is needed", which comes back to the 'please give us a "Fix It/..." leg up!'
Sure, I can script a "Shrink DB" but how often should I do it? Can I "ignore" that for "work" databases, not just for the Server?
There's obviously scope for enhancing the functionality and script generation (that could pop up in SSMS), so would you give this serious consideration?
Cheers!
When it comes to items such as Index Fragmentation I could persuade the powers that be to invest in I***a's Defrag Manager... Bet you could make a Rolls Royce version of that one... 8) According to a widely available Index Analysis script, I have 75 indexes per night that need some TLC. With reindex operations generating 2gigs of logs on 15 of those per night, on a mere 6gig db, you could say "Help is needed", which comes back to the 'please give us a "Fix It/..." leg up!'
Sure, I can script a "Shrink DB" but how often should I do it? Can I "ignore" that for "work" databases, not just for the Server?
There's obviously scope for enhancing the functionality and script generation (that could pop up in SSMS), so would you give this serious consideration?
Cheers!