Saving maintenance plans from prior versions using SSMS 2012 changes precedence constraint

• sqlprincess

  SSChasing Mays

  Points: 610

  More actions

  September 27, 2013 at 4:19 pm

  #278612

  I ran into strange behavior with SSMS 2012. Here's a test I did to verify it's a problem.

  I created a basic maintenance plan using SSMS 2005. I added a backup database task to backup the model database (as an example) to a folder that does not exist. I then added an execute t-sql statement task to send an email to me. I connected the backup task to the email task using the precedence constraint and set it to "failure" as well as a "logical or". I saved it and ran it to verify it will send me an email on failure. It did. I closed it.

  Next I opened up the maintenance plan using SSMS 2012 and set the reporting and logging to generate a file. I then saved the plan and closed it. I opened it again in SSMS 2005 to find the precedence constraint is now a "logical and". In SSMS 2012, it still shows as a "logical or". The reason I need the "or" is because my actual maintenance plans contain several tasks. They should be set to email us when any of the tasks fail, not all of them. When it's set to "and", we don't get an email when one of the tasks fails.

  Any ideas why this is happening? I have now learned (the hard way) to not edit or save maintenance plans in 2012 that were created in prior versions. I had the same problems with plans originally created in SQL 2000, 2008, and 2008 R2.

  Thanks!