Database Maintenance Planner

RE: Sql Server 2000
I am using the EM DB Maintenance Planner to set up maintenance for several
db's. In the dialog box I have checked 'yes' to 'Reorganize Data and Index
Pages' and 'Check DB Integrity', and also 'yes' to 'Perform these Checks
before doing Backups'. The dialog box then want's a time for doing these 'DB
Inegrity Checks, and I enter an appropriate, daily time.
Question: But later on in the dialog box it also asks for the time to do
daily Backups. Does this mean that I need to schedule enough time between
the 'DB integrity checks' and the 'Backup' to ensure Sql Server has enough
time to do the 'DB ingegrity checks'? Or does Sql Server ignore any time I
have entered for the 'DB Integrity Checks' since I have also checked 'Perform
these Checks before doing Backups'? If there is not enough time for Sql
Server to do the Integrity checks before the backup time, does it interrupt
the integrity checks to do the backup?
Thanks in advance for any clarification you can provide ...
bill
Thank you, Tibor ...
I decided to take your advise and uncheck the option that requires the db
integrity checks before each backup - I still run these checks, but way
ahead of the backups.
Thanks for your help ...
bill
"Tibor Karaszi" wrote:

> I don't think DBCC CHECKDB will block each other if you run two at the same time. But I don't have a
> 2000 instance with a database with enough size to test this (CHECKDB is largely re-written for
> 2005). But you can do that, having two windows size by size and executing at the same time.
> Agent or xp_sqlmaint (sqlmaint.exe) doesn't really care what commands are executed, so don't expect
> any intelligent handling at that level. I don't like the checkdb before backup option. Especially if
> you do log backups - you don't want to run a checkdb every 10 minutes...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "WCM" <WCM@.discussions.microsoft.com> wrote in message
> news:D25BD068-A8F3-440E-BF13-6CAF83DA0EDF@.microsoft.com...
>
>