Maintenance Plan Conversion Wizard

From RedGateWiki

Jump to: navigation, search

Contents

Introduction

The Maintenance Plan Conversion Wizard is a free utility for converting existing Maintenance Plans created with SQL Server 2000 and 2005 to utilize the functionality of SQL Backup.

Conversion Walkthrough

The conversion process

The conversion process breaks down into 6 steps:

  • Identify the SQL Server instance which contains the plans to convert
  • Identify one or more plans to convert
  • Configure any settings for new functionality provided by SQL Backup - for example compression and encryption settings
  • Review the changes
  • Apply the changes
  • Verify the changes

Identify the SQL Server instance

The first step of the wizard requests the name of the SQL Server instance that contains the maintenance plans to convert, it will also request the type of authentication required to connect to the instance.

  • The "..." button will display a list of SQL Server instances on the local network.

Image:Mpw serverselection.JPG
Image 1: Server Selection


Identify one or more plans to convert

The second step is to select one or more plans to convert. The wizard can convert both SQL Server 2000- and SQL Server 2005-generated maintenance plans, including legacy plans transferred from SQL Server 2000 to SQL Server 2005.

A list of plans will be displayed based on the following criteria:

  • The SQL Server agent job(s) associated with the maintenance plan are enabled;
  • The maintenance plan contains at least one valid native backup step (and if in SQL Server 2005, this step must be enabled);
    • If in SQL Server 2005, this step must be enabled;
    • A step is deemed to be "valid" if it contains at least one referenced database. Invalid or "incomplete" steps in SQL Server 2005 may refer to zero databases.

If the plan does not appear in the list, this could be because the plan has already been converted, or because it does not contain any convertible steps.

Image:Mpw plans.JPG
Image 2: Maintenance Plan Selection

If a backup plan contains more than one backup type (for example, a full and a differential step), the wizard will ask if all steps should be treated the same, or if different backup types should use different options.

Image:Mpw multipletypes.JPG
Image 3: Multiple Backup Types selected

Configure any settings for new functionality provided by SQL Backup

Because SQL Backup provides a variety of new features over what is available with native backups, some configuration options must be supplied to use these new features.

There are two required settings:

Six other settings are also available:

  • Overwrite existing files - if a file with the same name already exists, it will be replaced with the new backup.
  • Delete backup files older than ... - will delete any matching backups (that is, the same server, database and backup type) that are older than the timeframe specified.
  • Verify files after completion of backup - performs some additional checks on the file once it has been created to confirm that the backup has not been damaged or corrupted.
  • Compress backup - use compression to shrink the size of the backup file. Higher compression levels will generally product smaller files, but may take slightly longer to produce.1
  • Encryption options - use 128-bit or 256-bit encryption to secure the backup file from unauthorized users.1
  • Email completion log - will send an email either when the backup is completed, or if an error occurs (using the email settings configured in the SQL Backup 5 GUI).1

1 - subject to SQL Backup license - see http://www.red-gate.com/products/SQL_Backup/feature_comparison.htm for details of the SQL Backup versions available.


Image:Mpw options1.JPG
Image 4: Part 1 of the available settings

Image:Mpw options2.JPG
Image 5: Part 2 of the available settings

Review the changes

After the settings have been supplied, the wizard will provide a summary of the steps it will be performing. If you are happy with these, click "Start", otherwise click "Back".

The wizard will then indicate the progress that has been made, including raising any issues that may have occurred when converting the Maintenance Plans.

Image:Mpw review.JPG
Image 6: Review Changes

Verify the changes

Once the plan has been converted, it is recommended that the maintenance plan is checked to ensure it matches the expected outcome.

In SQL Server 2000 and legacy plans, a new plan and SQL Server Agent job will be created with the changes, and the old plan's SQL Server Agent job will be disabled.

In SQL Server 2005, the existing plan will be modified, disabling the steps involving native backups, and replacing them with steps involving SQL Backup. Any links or relationships between job steps should remain intact.

Image:Mpw converting.JPG
Image 7: Conversion Complete

Image:Mpw planbefore.JPG
Image 8: An example plan (before conversion)

Image:Mpw planafter.JPG
Image 9: An example plan (after conversion and reorganization)

Personal tools