Hi, We have a Database Integrity Job and Backup Job that are scheduled in a gap of 6 hrs, with the DI job kicking off first. However conidering the size of the DB- the DI job goes on running for about 9 to 10 hrs and ultimately causing both the jobs to fail. Any recomendations to make these job successful. I will be pressing to make the DI job run only on weekend, but still any suggestions will be helpful.
By database integrity, I'm assuming you mean a Database Consistency Check (DBCC) of the database? If that's taking 9 hours plus, you have a very large database, or, you have a lot of contention on resources. If the database is really large, you can break up the checks within DBCC to only do a physical check on a regular basis and then do the full check, as you already said, on weekends. To do the physical check, you'll need to modify the script so that it looks more like this: DBCC CHECKDB (mydatabase) WITH PHYSICAL_ONLY That checks all the page linkages in the database to ensure physical storage is correct. It doesn't check all the internal consistencies in the database storage, so you still need to do that. Another option is to do the physical checks online as suggested above and then do the logical checks against a restored copy of your database on another server. But, I'd also monitor the process to see if the DBCC is just being blocked by resource contention.