May 29, 2012 at 2:33 am
I have recently just deployed a new instance of SQL Server 2005 so we can move our development databases from SQL 2000 to SQL 2005.
After migrating the databases, I went ahead and created a new maintenance plan using SSMS 2012 (I manage SQL 2005, 2008 and 2012 instances so need to use the latest SSMS).
The new maintenance plan simply did a full backup of all databases on a daily basis. A maintenance clean up task was added to clear up old .bak files after 4 weeks.
When I went to save the Maintenance Plan, SSMS prompted me to choose whether to proceed and save this in 'the new format'. I chose 'Yes' as it told me it wouldn't affect it's execution.
However, this didn't work and seemed to create a corrupt maintenance plan and agent job.
When I tried to modify the maintenance plan, I got an error about an Index out of range. When I tried to modify the job I got an error about FK constraints in the msdb.dbo.sysmaintplan_subplans table!
The only way I could solve the issues was to drop the Maintenance Plan from SSMS 2005 (SSMS 2012 wouldn't drop the plan!).
Anyone else had this? Is it worth be writing up properly and submitting to MS Connect?
June 6, 2012 at 6:56 am
No-one got any thoughts on this?
I am not sure whether to post this to MS Connect or not?
Thanks,
Matt
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply