IDERA SQL Compliance Manager versions 4.5 and older. For installations of SQL Compliance Manager 5.0 and newer, including the IDERA Dashboard, see How to install SQL Compliance Manager and the IDERA Dashboard.


Before installing IDERA SQL Compliance Manager, consider the following best-practices:

  • Ensure you review the hardware, software, permissions, and port requirements.
  • Decide whether you should install the Collection Server on a dedicated SQL Server instance.
  • If you plan to audit instances running SQL Server 2005 or later, install the Collection Server on a computer hosting the highest version of SQL Server running in your environment. For example, to accept event data from audited instances running SQL Server 2012, the Repository databases must reside on a SQL Server 2012 or higher instance.

By default, SQL Compliance Manager installs with a trial license. For more information about trial licenses or upgrading your license, see Licensing.

To install SQL Compliance Manager:

  1. Log on with an administrator account to the computer on which you want to install SQL Compliance Manager.
  2. Run SETUP.EXE in the root of the installation kit.
  3. On the IDERA SQL Compliance Manager Quick Start window, click SQL Compliance Manager to begin the installation process.
  4. On the Welcome to the Setup Wizard for IDERA SQL Compliance Manager window, click Next.
  5. Read the Trial Software License Agreement, select I accept the terms in the license agreement and click Next to continue.
  6. Accept the default folder for your SQL Compliance Manager installation, or click Browse to specify a different folder.
  7. Select whether you want the SQL Compliance Manager application to be available to all users who log on to this computer, and then click Next.

    If you select this option …Setup configures the user logon profile to …
    Anyone who uses this computerDisplay icon on desktop when anyone logs onto this computer using a valid domain user account
    Only for meDisplay icon on desktop only when the current user account logs onto this computer
  8. Select the appropriate setup type, and then click Next.

    Setup TypeDescription
    TypicalAllows you to install all SQL Compliance Manager components on this computer
    Console OnlyAllows you to install only the SQL Compliance Manager Management Console
    Agent OnlyAllows you to install only the SQL Compliance Manager Agent
    CustomAllows you to select the individual SQL Compliance Manager components you want to install
  9. If you chose the Custom type, select one or more SQL Compliance Manager components, and then click Next. Using the Custom setup type, you can install SQL Compliance Manager components in the following ways:
    • Collection Server and Repository with SQL Compliance Manager Agent
    • Collection Server and Repository
    • Management Console with SQL Compliance Manager Agent
    • Management Console only
    • SQL Compliance Manager Agent only

      The setup program installs the Repository when you install the Collection Server.

      To install all SQL Compliance Manager components at the same time, use the Typical setup type.

  10. If you chose to install the Collection Server and SQL Compliance Manager Agent using the Typical or Custom setup, complete the following procedure:
    1. Specify the location where you want the Collection Server to store audit data received from the SQL Compliance Manager Agent, and then click Next. The specified folder is the trace file directory on the Collection Server.
    2. Specify the Windows user account that you want the Collection service and SQL Compliance Manager Agent to run as to access the Repository, and then click Next.
    3. Click Browse to select the SQL Server instance on which you want to install the Repository. The setup program creates the Repository databases on the specified instance.
    4. Specify the authentication the setup program should use to connect to the selected SQL Server and create the Repository, and then click Next.
    5. If you want to audit the Repository or other databases associated with the selected SQL Server instance , click Yes, and then click Next.
    6. Specify the location where the SQL Compliance Manager Agent should store collected audit data, and then click Next. The specified folder will be the trace file directory on the audited SQL Server instance.
    7. Select whether you want to start the services immediately after install, and then click Next.
  11. If you chose the Agent Only setup, complete the following procedure:
    1. Specify the location where the SQL Compliance Manager Agent should store collected audit data, and then click Next. The specified folder will be the trace file directory on the audited SQL Server instance.
    2. Specify the Windows user account the SQL Compliance Manager Agent service should run as to access databases associated with the audited SQL Server instance, and then click Next If you are installing the agent on a computer that belongs to a workgroup or non-trusted domain , specify a valid local account (MyComputer\AccountName).
    3. Type the name of the computer on which the Collection Server is installed, and then click Next If you are installing the SQL Compliance Manager Agent on a workstation or a computer that belongs to a non-trusted domain , the setup program is unable to validate a connection to the specified computer. Click No when prompted to specify another Collection Server computer.
    4. Click Browse to select the SQL Server instance you want to audit, specify the authentication the SQL Compliance Manager Agent should use to connect to associated databases, and then click Next.
    5. Select whether you want to start the SQL Compliance Manager Agent service immediately after install, and then click Next.
  12. Click Install.
  13. Click Finish. If you chose a typical setup, select Launch Idera SQL Compliance Manager to begin auditing your SQL Server environment.


The SQL Compliance Manager installer detects if the local machine has an older version of the SQL Server 2012 Native Client installed, and if needed SQL CM upgrades the Native Client to the latest version and proceeds with installation. If no Native Client is installed on server, then SQL CM installs the latest Native Client version and proceeds with installation.



IDERA | Products | Purchase | Support | Community | Resources | About Us | Legal
  • No labels