SQL Diagnostic Manager consists of a light, unobtrusive architecture that easily runs in your SQL Server environment with minimal configuration. All SQL Diagnostic Manager components run outside and separate from SQL Server processes.

SQL Diagnostic Manager Console

Use the SQL Diagnostic Manager Console to:

The SQL Diagnostic Manager Console retrieves historical information directly from the SQL Diagnostic Manager Repository. All real-time requests use the SQL Diagnostic Manager services to poll the monitored SQL Server.

SQL Diagnostic Manager Services

SQL Diagnostic Manager has three centralized services, the Management Service, the Collection Service, and the Predictive Service. These three services reside on the same computer.

The Management Service

The Management Service performs the following primary functions:

The Collection Service

The Collection Service performs on-demand and scheduled collection from the monitored SQL Servers.

The Predictive Service

The Predictive Service is used for Alert Forecasting and performs the following primary functions:

SQL Diagnostic Manager Plug-in

When SQL Diagnostic Manager is registered with the IDERA Dashboard, the product plug-in module is deployed. The SQL Diagnostic Manager plug-in consists of web views and widgets and a .NET based add-in module (SQL Diagnostic Manager add-in). The web views and widgets are deployed in the Web Application Service of the IDERA Dashboard, and the SQL Diagnostic Manager add-in in the Core Service of the same.

The Web Application Service dynamically loads in SQL Diagnostic Manager's views and widgets and makes them available to web console users.  The views and widgets use the SQL Diagnostic Manager add-in REST APIs to retrieve data.  Likewise, the SQL Diagnostic Manager add-in retries data from the product services and Repository.

SQL Diagnostic Manager Web Console integrated to the IDERA Dashboard

The IDERA Dashboard and SQL Diagnostic Manager web console are automatically installed upon upgrade or during installation of the 9.0 or higher versions.

To access the web console:

  1. Open your selected Browser, make sure it is compatible with the SQL Diagnostic Manager web console requirements.
  2. Type the SQL Diagnostic Manager product URL: http://<machinename>:<port> where <machinename> is the name of your host or machine, and <port> is the port specified during installation.  The default URL is http://<localhost>:9290.
  3. When the SQL Diagnostic Manager web console launches on your browser, use your Windows user account <domain\user> with the respective password to log into the product.

To learn about the new components and architecture, hardware and software requirements, and the required accounts and permissions you need to run the IDERA Dashboard and SQL Diagnostic Manager web console in your environment, see Deploy the IDERA Dashboard and SQL Diagnostic Manager.

The IDERA Dashboard Web Application service comes with SSL already set up. For more information on running the IDERA Dashboard over SSL, see

SQL Diagnostic Manager Repository

The SQL Diagnostic Manager Repository is a centralized SQL Server database that stores collected metrics on a scheduled basis, historical data, and alerts information. The SQL Diagnostic Manager Repository also stores configuration information, such as the credentials used to monitor a registered SQL Server instance.

SQL Diagnostic Manager 10.1 and later requires Microsoft SQL Server 2005 or above running on the computer that hosts the SQL Diagnostic Manager Repository database for all installations.

Authentication in SQL Diagnostic Manager

SQL Diagnostic Manager uses the same types of authentication available in the SQL Server security model. When specifying account credentials for the SQL Diagnostic Manager services, you can use Windows Authentication or SQL Server Authentication.

When considering which authentication to use, keep in mind that SQL Server Authentication is required when no domain trust exists between the SQL Diagnostic Manager Services computer and the computers hosting the monitored SQL Server instances. For example, if the monitored SQL Server instances are located in an untrusted domain or behind a firewall, you must use SQL Server Authentication to successfully deploy SQL Diagnostic Manager. In this case, you must use the sa account or a SQL Server login that has System Administrator permissions.

For more information about these authentication types and the SQL Server security model, see the Microsoft document, Authentication in SQL Server.


SQL Diagnostic Manager identifies and resolves SQL Server performance problems before they happen. Learn more > >
IDERA WebsiteProductsPurchaseSupportCommunityAbout UsResources Legal