Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am searching for Database Health check articles specifically for a web application back-end server and SQL Server 2005/2008.

My current checklist includes:
- Index Fragmentation
- SQL Server logs
- Mirroring Monitor
- Backup completion
- File growth

What else should I look for? Are there good articles specifically for a webapp DBA scenario?

(Note: I don't need to worry about many database users - there is only one user the application itself)

share|improve this question
2 – Aaron Bertrand Jul 20 '12 at 21:05
Also see Glenn Berry's diagnostic scripts here: – Aaron Bertrand Jul 20 '12 at 21:06
up vote 4 down vote accepted

The two I've found most useful:

Posting these as an answer since you haven't received any other responses. Also, not sure how long this question will live; it may be viewed by some as a shopping list request that will eventually be obsolete.

share|improve this answer
Since this is for SQLServer 2005/2008, which aren't likely to have many more changes now that 2008R2 and 2012 are the "main branches", I think that the existing legacy codes are sufficient, and there really aren't a lot of shopping list options available here. Better to document the few good resources that everyone turns to so we can close as dupe, as need be. The mods discussed this in and we feel this is fine. (No meta post, only one question does not a meta make) – jcolebrand Jul 25 '12 at 15:30
@jcolebrand Right but Brent's and Glenn's scripts may disappear, they may move to a different web site, etc. – Aaron Bertrand Jul 25 '12 at 15:48
So very true, but if you're supporting Sql 2005 and don't have some way to get access to Brent Ozars script (which will live on, I'm sure) then ... maybe it's time to upgrade to Sql Server 2018? – jcolebrand Jul 25 '12 at 15:51

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.