SQL SVR 7 on W2K
We use weekly maintenance plans to check integrity, rebuild indices and automatically repair minor errors on all system db's. They're backed up every night.

Same weekly maintenance on production DB's with nightly backup and hourly log file backups.
This allows us to restore to any point-in-time.

-----Original Message-----
From: Melissa Faga [mailto:[Email Address Removed] Wednesday, August 14, 2002 9:40 AM
To: [Email Address Removed] database integrity checks


Can anyone suggest a course of action to make sure that both my user and
system databases are okay and don't have any errors? We had been using a
separate program to run backups and to run what they call consistency checks
to make sure the databases are in good shape before the backups. I believe
the backup software runs a series of DBCC commands such as checkdb.
Anyways, we had a situation a week ago where are server was rebooted and SQL
would not restart. We investigated and came to the conclusion that the
master database was corrupt even though it had passed our checking.

I am looking for a recommendation on what checks I should run to ensure that
our databases are not corrupt.

Thanks in advance,
Melissa


Melissa Faga
GIS/DB Manager
City of Redmond
425-556-2134
[Email Address Removed] unsubscribe, e-mail: mssqldba-[Email Address Removed] additional commands, e-mail: mssqldba-[Email Address Removed]MS Sql Server LazyDBA home page