Page History
...
Tip |
---|
SQL Diagnostic Manager 10.2 3 requires Microsoft SQL Server 2005 or above running on the computer that hosts the SQL Diagnostic Manager Repository database for all installations. |
...
Info |
---|
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 |
|
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 |
General requirements
The following requirements apply for all SQL Diagnostic Manager components.
Type | Requirement |
---|---|
CPU | 2.0 GHz or higher |
Memory | 1 GB |
Operating System (32-bit and 64-bit) |
|
|
| |
Port Access | 5166, 5167, 5169 |
Client Browser | Internet Explorer 7.0 or later |
Production requirements
Consider the following requirements when installing SQL Diagnostic Manager in an environment where the components are on separate computers.
...
...
SQL
...
SQL Diagnostic Manager Console
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. |
Software Framework | Microsoft .NET 4.0 |
+ and MDAC 2.8 | |
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 | System Administrator privileges on the monitored SQL Server instances |
Management Service Permissions | System Administration privileges on the SQL Diagnostic Manager Repository instance |
Software Framework | Microsoft .NET 4.0 SP2+ |
and MDAC 2.8 |
SQL Diagnostic Manager Repository
Tip |
---|
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 Edition |
|
...
...
Monitored SQL Server Instances
Type | Requirement |
---|---|
SQL Server Standard or Enterprise Edition |
|
|
|
Info | ||
---|---|---|
| ||
To monitor an Amazon RDS instance using SQL Diagnostic Manager, you have to create a SQL Server user on the instance with the following permissions: Roles: public Other permissions (under the Securables tab when using SSMS): View server state, View any definition, View any database, and Connect SQL. |
...
|
This topic provides the minimum requirements for installing SQL Diagnostic Manager. For more information about installation requirements, view SQL Diagnostic Manager Hardware Sizing guidelines.
...