Database Maintenance Plan not saving Integrity Options

Last Post 11 Jun 2008 07:03 AM by Amber_Robertsona. 5 Replies.
AddThis - Bookmarking and Sharing Button
Author Messages
Amber_Robertsona
New Member
New Member

--
10 Jun 2008 03:46 AM
Dear DBAs, I am having a strange problem with the Integrity tab on an existing SQL server 2000 Database Maintenance Plan. If I place a tick in 'Perform these test before backing up the database or transaction log' option and click apply and o.k. it doesn't seem to save the change and doesn't give me an errors. However if I create a new Database Maintenance Plan it does save the change.

Does anybody know why this is happening? Also does anybody know how to update this on existing Database Maintenance Plans?


Any suggestions much appreciated.

Kind Regards
Amber
Amber_Robertsona
New Member
New Member

--
10 Jun 2008 07:15 AM
Hi, thank you for your speedy reply.

I want to check this option as I thought it would check the database consistency before performing a backup therefore preventing the system creating rubbish database backups. Let me know if you want more details.


Regards
Amber
Amber_Robertsona
New Member
New Member

--
11 Jun 2008 12:18 AM
Some servers are using SP3 and some SP4.

Amber_Robertsona
New Member
New Member

--
11 Jun 2008 07:03 AM
Same problem on all the SQL2000 servers. Not sure if it is helpful, but if I create a new Database Maintenance Plan it does save the option if I haven't already executed the associated backup job. If I try to select this option afterwards it doesn't save it. Let me know if you would like more details.


Regards
Amber
Amber_Robertsona
New Member
New Member

--
11 Jun 2008 11:48 PM
I updated the plans from my client machine not logging onto each individual server. I will give it a go and see if it makes a difference.
Amber_Robertsona
New Member
New Member

--
12 Jun 2008 12:00 AM
Hi, I have tried updating an existing Database Maintenance Plan directly on the server but still having the same problem.

In reply to gunneyk, I thought if the job found Integrity issues it would stop the backup job therefore alerting us there is a problem. We check backup status daily, therefore if it does fail we still have the option to perform a manual backup if a problem is found. We can feel certain that all our previous database backups are clean perform doing restore. Fair point about running dbcc many times as a Database Maintenance plan also include transaction backup jobs which run serveral times a day. I will give this some futher thought.
Thank you both for your help so far.

Regards
Amber


Acceptable Use Policy
---