January 6, 2004 at 11:55 am
Weird problem with Database Maintenance Plan....
I will mention this problem I am having with one our servers. This server has several databases and four maintenance plans that schedule the backup, integrity and optimizations.
Now for only one of these plans, the rest of the plans are identical, on this server when I select the option "Perform these tests before backing up the database or transaction log" in the "Integrity" tab and save it, it does not stay selected. By that I mean, if I go back to the maintenance plan properities and check if the option is selected, it shows that it is not. While I had just selected the option a moment ago and saved it.
I realized this when the integrity jobs did not run before the backups as they used to. So, somehow this option got unselected and cannot be selected anymore.
On another server, there are three maintenance plans and all of them have the same problem. No matter what I do, I cannot save the plan with that option.
To give you guys some background, I already SP3 applied to all these SQL2000 servers running on Windows 2000. Also, these plans used to work fine before. For sometime, I have had some problems like these with my local installation of SQL server but not on our production boxes. Now it seems like the problem has propogated to them too.
Has anyone come across anything like this. Any help or direction would be appreciated. Thanks in advance.
January 6, 2004 at 3:13 pm
I have experienced a similar problem with a maintenance plan while using SQL7. The only way I could remedy the issue in 7 was to recreate the maintenance plan using the exact parameters I wanted. If I tried to modify an existing plan I would see similar issues to what you described.
I have however since upgraded to SQL2000 SP3 and have not noticed any issues like this. You may want to try rebuilding the maintenance plan as I had to do in 7.
I also did do some research and found that you can edit the actual command lines or steps to your maintenance plan. I tried this also but with no luck.
January 8, 2004 at 4:16 pm
I already am using SQL2000 with SP3, but still the problem. I have had SP3 for a little while now, but the problem only surfaced a couple days ago.
Well, I found a solution though. I modidied the Jobs associated with the Maintenance Plans, directly by adding the options '-BkUpOnlyIfClean -CkDB ' to the xp_SQLMaint command. Even the associated Maintenance Plan showed the appropriate option selected.
Thanks for taking time to answer my question.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply