October 23, 2013 at 10:02 am
The db check takes 4 hours and the backup itself takes 10 mins. What are your thought's on when u should and when u shouldn't do a full db check before backup?
I've never used it before. however, they're using it at my current place and am contemplating rmoving it
October 23, 2013 at 10:33 am
If you have a mechanism to test the backup, meaning restore it, then you could do a physical only check on the live database which is much faster. Then, you restore the backup to another server and run the logical parts of the consistency check which are much longer and usually the cause of long running checks.
I wouldn't suggest completely abandoning the consistency checks because if you get corruption, you could be facing the loss of all data in the database.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
October 23, 2013 at 10:34 am
I do it often enough so I can quickly recover from a clean backup, so if I have 3 days worth of backups on the server, I checkdb every 3 days, and so on.
4 hours to run checkdb but only 10 mins to backup seems incongruous, I would check that out, what command do you actually run for the checkdb?
---------------------------------------------------------------------
October 23, 2013 at 10:43 am
Before you remove it, ask whether you want to back up a corrupt database. Ask whether you have any way at all to check for corruption and if not whether you want to bet your company's data and your job on your database not becoming corrupt at any time.
My answer's here (in the first 50 minutes): http://www.youtube.com/watch?v=SQ5Pw1jeWdY&list=PLoGAcXKPcRvbTr23ujEN953pLP_nDyZJC&index=40
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
October 23, 2013 at 10:44 am
george sibbald (10/23/2013)
4 hours to run checkdb but only 10 mins to backup seems incongruous, I would check that out, what command do you actually run for the checkdb?
And what command do you run for the backup?
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 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply