Noticing problems early.
WHAT TO WATCH
Total size, and its growth rate The largest tables Query performance on key pages Connection errors in the log
SIZE GROWTH
A database growing steadily with your content is normal.
A database that doubled in a month without a corresponding increase in content is bloat, and worth investigating.
TABLE SIZES
Review the largest tables quarterly. A table that has become the largest without a good reason is usually a log or statistics table.
PERFORMANCE
Time a key page periodically. A page that was fast and is now slow frequently indicates a table that has grown past the point where an unindexed query remains acceptable.
ERRORS
Connection errors, too many connections, and timeout messages in the log all indicate pressure.
WHAT TO ACT ON
Unexpected growth A page that has become noticeably slower Repeated connection errors
WHAT NOT TO WORRY ABOUT
Gradual growth matching your content Occasional slow queries during heavy operations
THE PRACTICAL ROUTINE
A quarterly look at sizes and a monthly backup check covers most of it.
