There are three types of SQL Diagnostic Manager installation (Trial, General, and Production). Refer to the following list of requirements for each type of installation.
SQL Diagnostic Manager 10.5 requires Microsoft SQL Server 2005 or above running on the computer that hosts the SQL Diagnostic Manager Repository database for all installations. |
Tempdb monitoring is supported on SQL Server 2005 and above servers only. |
To run PowerShell scripts, upgrade to PowerShell 3.0 or higher. This upgrade is required to use the PowerShell snap-in. |
Consider the following requirements when installing all SQL Diagnostic Manager components on one computer.
Type | Requirement | |
|---|---|---|
SQL Server Standard or Enterprise Edition |
Only on Windows and Linux
| |
Hard Disk Space | 200 MB for all SQL Diagnostic Manager components | |
Windows Permissions | Your Windows Logon account includes local Administrator permissions | |
SQL Server Privileges | Either a Windows user account or SQL Server login that includes System Administrator privileges on the monitored SQL Server instances |
The following requirements apply to all SQL Diagnostic Manager components.
Type | Requirement |
|---|---|
CPU | 2.0 GHz or higher |
Memory | 1 GB |
Operating System 64-bit |
|
Port Access | 5166, 5167, 5169 |
Client Browser | Internet Explorer 7.0 or later |
Consider the following requirements when installing SQL Diagnostic Manager in an environment where the components are on separate computers.
Type | Requirement |
|---|---|
Disk Space | 40 MB |
SQL Server Permissions | Your Windows login account includes Read Access to the SQL Diagnostic Manager Repository. You can specify a SQL Server login instead. |
Monitor Resolution | 1280 x 1024 with small text for the best viewing of the SQL Diagnostic Manager Dashboard |
SQL Diagnostic Manager Services
Type | Requirement |
|---|---|
Disk Space | 50 MB |
Collection Service Permissions | For more information, review the User Creation Scripts. |
Management Service Permissions | Sysadmin fixed server role on SQL Diagnostic Manager Repository instance |
| Windows Runtime Components |
|
SQL Diagnostic Manager 11.0 installer checks for your current .NET framework version and prompts the required .NET update. After installing the latest version of .NET Framework you need to reboot your machine; otherwise, SQLDM installation fails. |
SQL Diagnostic Manager 7.2 and later includes a repository autogrow setting at 32 MB, which is sufficient for trial and small environments in production. Environments with larger, multi-server installations should change the repository autogrow setting to 250 MB or higher to prevent frequent data file autogrow, which can cause performance problems. Using percentage-based autogrow is not recommended. |
Type | Requirement | |
|---|---|---|
Disk Space | 1GB to 3GB for one year of data per monitored SQL Server instance | |
SQL Server Standard or Enterprise/Datacenter Edition |
Only on Windows and Linux
| |
| Cloud Deployment |
|
Type | Requirement | |
|---|---|---|
SQL Server Standard or Enterprise/Datacenter Edition |
Only on Windows and Linux
| |
| Cloud Deployment |
|
Review the Minimum and Recommended Permissions for Amazon RDS and the Minimum and Recommended Permissions for Azure SQL to create a SQL Server user on the server to monitor a cloud instance. |
This topic provides the minimum requirements for installing SQL Diagnostic Manager. For more information about installation requirements, view SQL Diagnostic Manager Hardware Sizing guidelines.
The IDERA SQL Diagnostic Manager Management Pack for integration with SCOM is designed for System Center Operations Manager 2007 R2 and above. For more information about SQL Diagnostic Manager MP and SCOM installation, see Install and configure the SQL Diagnostic Manager Management Pack for SCOM.
SQL Diagnostic Manager for SQL Server performance monitoring, alerting, and diagnostics for SQL Server. |