March 25, 2013 at 5:08 am
We have a db that has a mission critical website sitting on top of it. We check it weekly with a DBCC CHECKDB command, which takes 1 to 2.5 minutes to run. Are web users likely to see issues during that time? If so, is there a better way to do a weekly health check on it?
March 25, 2013 at 5:29 am
Whats your RTO and RPO for the database? If its mission critical and DBCC CHECKDB only takes 1 - 2.5 minutes to run, I would run it every day not weekly. The only impact to the users would be while the snapshot is being created that DBCC CHECKDB runs on, so will be very minimal.
March 25, 2013 at 6:17 am
CheckDB is an online operation. Users may note slow down, but that's all.
Better question, if your database becomes corrupt, how soon do you want to find out about it and how long do you retain your backups?
If you do find corruption, restore from backup should always be an option and that means doing integrity checks often enough that restore from a clean backup is always possible
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
March 25, 2013 at 6:19 am
anthony.green (3/25/2013)
The only impact to the users would be while the snapshot is being created that DBCC CHECKDB runs on, so will be very minimal.
The creation of the snapshot won't affect any users. The impact from checkDB is the process of running the checks after the snapshot has been created, because of the IO and CPU load from CheckDB
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
March 28, 2013 at 3:07 am
Anthony and Gail,
Thanks very much for our comments. You have reassured me.
Best wishes
Mark
March 28, 2013 at 3:32 am
I restore backup another server and then i make checkdb
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply