Inevitably, there are a bunch of tables that:
- Tables whose names start with “temp” or “backup” or “just_in_case”
- Tables with no clustered index that were clearly created with a select-into, and then forgotten about
- Tables that haven’t been accessed in months or years
We have some chuckles, make a quick calculation, and realize that our database is 10%-20% larger than it needs to be. That means our backups are taking 10-20% longer, corruption checking, restore testing, backup space, disaster recovery test time, you name it – it’s all 10-20% higher.
So now if SQL ConstantCare® sees a new table with at least a million rows, we give you a heads-up in your daily email:
This is such a good example of what SQL ConstantCare® is all about: giving you practical insight, not just raw metrics.