In the maintenance plans Integrity tab there is a check box for: "Preform
these tests before backing up the database, or transaction logs".
I want to be sure I understand this. If I check this box, does that mean an
integrity check (and potentially a repair) will run ANYTIME a database, OR
transaction log backup is run, as part of the backup procedure and that one
would not need to set a schedule for the integrity checks?
Given the posibility of the function locking the database (to do a repair),
I don't know if this is a good idea, or not.JayKon wrote:
> In the maintenance plans Integrity tab there is a check box for: "Preform
> these tests before backing up the database, or transaction logs".
> I want to be sure I understand this. If I check this box, does that mean a
n
> integrity check (and potentially a repair) will run ANYTIME a database, OR
> transaction log backup is run, as part of the backup procedure and that on
e
> would not need to set a schedule for the integrity checks?
> Given the posibility of the function locking the database (to do a repair)
,
> I don't know if this is a good idea, or not.
Checking that box means that the maintenance plan will perform an
integrity check before running a backup. Running a backup manually,
from QA for instance, will NOT invoke an integrity check. I would
suggest NOT using this option.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Checking that option will verify the allocation and structural integrity of
user and system tables, and indexes in the database.
This will incur lots of resource usage and will lock resouces in SQL 2000.
So I recommend you to schedule a DBCC CHECKDB during offpeak time.
Thanks
Hari
"Tracy McKibben" wrote:
> JayKon wrote:
> Checking that box means that the maintenance plan will perform an
> integrity check before running a backup. Running a backup manually,
> from QA for instance, will NOT invoke an integrity check. I would
> suggest NOT using this option.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>|||What I thought, thanks guys.
"Hari Prasad" wrote:
[vbcol=seagreen]
> Checking that option will verify the allocation and structural integrity o
f
> user and system tables, and indexes in the database.
> This will incur lots of resource usage and will lock resouces in SQL 2000.
> So I recommend you to schedule a DBCC CHECKDB during offpeak time.
> Thanks
> Hari
> "Tracy McKibben" wrote:
>
Monday, March 12, 2012
Maint plan: integerity check & backup
Labels:
backing,
backup,
box,
database,
integerity,
integrity,
logs,
maint,
maintenance,
microsoft,
mysql,
oracle,
plan,
plans,
preformthese,
server,
sql,
tab,
transaction
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment