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

Before updates of our application, I run some checks on the database like CheckAllocations and CheckCatalog, so I know the database is in good shape before the update scripts get executed.

What is recommended for checks like that? How often should they be executed?

Do we need more checks besides these two?

We used to run the CheckIdentityValues as well, but I removed that, because that method will be removed (according to MSDN).

share|improve this question

migrated from Dec 5 '11 at 11:36

This question came from our site for professional and enthusiast programmers.

up vote 1 down vote accepted

For me, it depends on your maintenance window and usage. It takes time and resources to run the DBCC checks so you want to minimise imnpact on a running app

If you can run it every night, do so. Otherwise weekly.

Or monthly if you really are 24/7.. but then I'd be running DBCC on a restored database as an extra check.

And you have to consider other maintenance too: indexes and statistics in your window

share|improve this answer
The indexes are rebuild or reorganized every night, depending on the fragmentation. What do you suggest for table statistics? – Erik Dekker Dec 21 '11 at 10:26
@ErikDekker: index statistics are done with index rebuilds. I'd do column statistics more often – gbn Dec 21 '11 at 10:32

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.