Upgrading SQL Defrag Manager allows you to take advantage of the new features available in the latest version.
To successfully upgrade your Microsoft SQL Server environment to this build, complete the procedures outlined in the following table. These procedures support upgrades from SQL Defrag Manager versions 2.0 or later.
|Follow these steps|
|Ensure the computers on which you want to upgrade SQL Defrag Manager meet or exceed the product requirements for SQL Defrag Manager. For example, ensure .NET Framework 2.0 SP1 or later is running on the target computer.|
|Ensure your Windows logon account has local administrator permissions on the computers you intend to upgrade.|
|Review the product architecture.|
|Review the supported installation scenarios and identify the appropriate upgrade path for your environment.|
|Close all open applications on the computers you intend to upgrade.|
|Upgrade your SQL Defrag Manager installation.|
Available upgrade paths
Because you can install each component separately on different computers, the type of upgrade you need to perform depends on your environment. The following table describes the conditions under which you would follow a typical or staged upgrade path.
|Environment description||Recommended path||Why|
|Simple environment, where the SQL Defrag Manager Console, the Repository, and the Management Service all reside on the same computer||Typical|
A simple environment can be upgraded through the setup program.
Distributed environment, where each SQL Defrag Manager component resides on a different computer.
A distributed environment requires a staged upgrade to maintain continuity while each component is upgraded.
Multiple Management Consoles deployed to different computers.
A SQL Defrag Manager installation with multiple Management Consoles requires a staged upgrade to maintain continuity while each component is upgraded.
Change control policies that require multi-phased upgrades.
An environment with stringent change control policies requires a multi-phased upgrade in order to test each updated component thoroughly before moving on to the next step.