July 13, 2011 at 8:44 am
Hi,
We are running maintenance job of database integrity check for multiple servers every week. But we do not analyse the output and infact it is not possible to check each report of DBCC CHECKDB for large number of SQL servers.
DBCC CHECKDB (database name) - This is informational and does not removes any error until we use the other options to correct a corrupted database. So is it wise to have this job or what is the best way to find corruption in any database in a large environment?
Ryan
//All our dreams can come true, if we have the courage to pursue them//
July 13, 2011 at 9:06 am
Yes, it's absolutely essential to have that and to check that it runs clean when it runs.
Without that you have no way of finding corruption until some query trips over it and the user reports it, and by that point it may no longer be possible to recover without data loss.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply