SOLVED

Maintenance plan missing after editing in a second window

Brass Contributor

I was editing a maintenance plan, but I had the same plan already open in another window but not saved, and I just forgot and opened a second window of the same plan.

 

When I saved the edits in the second window I had open, it errored, and the plan would no longer open afterward.  So I disconnected and reconnected to the SQL instance and the plan is gone. So I don't have the error, but it said something about a value being null.

 

Why does this happen and how can I restore the plan?

6 Replies
Could You please check in job activity monitor in SQL Server Agent Where you may get it
best response confirmed by Leavii (Brass Contributor)
Solution

how can I restore the plan?


@Leavii , the SSIS packages for maintenance plans are stored in system-database "msdb". If you have a good backup, you could restore it under a new name and copy over the missing informations

 

SELECT [name]
      ,[id]
      ,[description]
      ,[createdate]
      ,[folderid]
      ,[ownersid]
      ,[packagedata]
      ,[packageformat]
      ,[packagetype]
      ,[vermajor]
      ,[verminor]
      ,[verbuild]
      ,[vercomments]
      ,[verid]
      ,[isencrypted]
      ,[readrolesid]
      ,[writerolesid]
  FROM [msdb].[dbo].[sysssispackages]

 

@Arshad440 

Not in job activity monitor.

@olafhelper 

I will give this a shot.  I recreated the plan, but I know I will do this again as I have done it before.  I feel like I remember doing something different to get the job back though.  Doesn't seem to be an issue in SSMS 19, but 12 so I will just avoid that version going forward.

You should avoid maintenance plans as it at all, they have never been reliable.

@olafhelper 

Have always worked for me.

1 best response

Accepted Solutions
best response confirmed by Leavii (Brass Contributor)
Solution

how can I restore the plan?


@Leavii , the SSIS packages for maintenance plans are stored in system-database "msdb". If you have a good backup, you could restore it under a new name and copy over the missing informations

 

SELECT [name]
      ,[id]
      ,[description]
      ,[createdate]
      ,[folderid]
      ,[ownersid]
      ,[packagedata]
      ,[packageformat]
      ,[packagetype]
      ,[vermajor]
      ,[verminor]
      ,[verbuild]
      ,[vercomments]
      ,[verid]
      ,[isencrypted]
      ,[readrolesid]
      ,[writerolesid]
  FROM [msdb].[dbo].[sysssispackages]

 

View solution in original post