You can easily and quickly install SQL Defrag Manager on any computer that meets or exceeds the following hardware, software, and permission requirements. Consider the following requirements when installing SQL Defrag Manager in a typical environment.
Idera is phasing out all Itanium support in SQL Defrag Manager 3.0 and all subsequent versions. SQL Defrag Manager 3.0 does not support the Itanium processor architecture and limited technical support is available through November 2012.
General product requirements
All SQL Defrag Manager components require the following software:
- Microsoft .NET Framework version 2.0
- MDAC 2.8 or later
- Windows Installer 3.1 or later
Typical installation
A typical installation sets up all SQL Defrag Manager components on the same computer. The following table lists the requirements for a typical installation.
| Type | Requirement |
|---|---|
| CPU | 2 GHz |
| Memory | 2 GB |
| Hard disk space | 30 GB for the Repository |
| Operating system | One of the following operating systems:
|
Microsoft SQL Server (Repository) | One of the following versions of Microsoft SQL Server:
|
Microsoft SQL Server (Managed Server) | One of the following versions of Microsoft SQL Server:
|
Console-only installation
A Console-only installation installs the SQL Defrag Manger Console. The Console-only installation assumes that a full installation already resides on another computer. The following table lists the requirements for a Console-only installation.
| Type | Requirement |
|---|---|
| CPU | 2 GHz |
| Memory | 2 GB |
| Operating system | One of the following operating systems:
|
Management Service permission requirements
The Windows user account used by the Management Service requires the following permissions to access the SQL Server instances you want to manage.
| Type | Requirement |
|---|---|
| Windows permissions | Local Administrator permissions on the computer hosting the Management Service. |
| SQL Server privileges | A member of the sysadmin fixed server role in the SQL Server instance hosting the Repository and on each managed SQL Server instance. |