• Make sure the core modules, such as the Module-Manager, are up-to-date on all servers since not all module dependencies are validated during the SolutionPack installation. The installation guide for your product provides more information.
  • Ensure you create a watch4net user prior to installing the SolutionPack. You may need this to ensure correct credentials are added to Microsoft SQL Server Devices Management during the installation process.


  1. Log in to your product and click Administration > Centralized Management.
  2. Click SolutionPacks and select SOLUTIONPACK CENTER.
  3. Select the SolutionPack for Microsoft SQL Server in the Browse and Install SolutionPacks window.
  4. Read the summary information and click Install.
  5. Type the instance name.
  6. Assign a server for each of the components.
  7. Click Next.
    The window displays pre-configured alerts details.
  8. From the Pre-Configured Alerts drop-down menu, select existing settings that have been specified for other components, or select Add a new alerting on data collection.
  9. Click Next.
    The window displays the data collection details.
  10. Make a selection in the Data Collection drop-down menu.
    Select existing settings that have been specified for other components or select Add a new data collection.
  11. If you select Add a new Data collection, type information about the data collection. In the Hostname or IP address to send data field, use localhost on default port 2020.
    This is the Collector host where the Load Balancer Connector is installed.
  12. Select the Frontend Web Service option.
    Select existing settings that have been specified or choose Add a new Frontend Web Service.
  13. If you select Configure Collector advanced settings, you have the option to select different polling periods.
    The default polling period is 15 minutes. Consult with your database administrator to set the polling period based on the number of SQL Server instances that are being polled by this collector manager instance. For example, you have the option to select 5 minutes, 15 minutes, 30 minutes, or one hour.
  14. Click Next.
  15. If you select Add a new Web-Service Gateway, type information about the web-service gateway.
  16. In the Administration Web-Service instance, select an existing instance or create a custom instance.
  17. Click Install.
  18. Click OK.

    Monitor the installation logs to ensure that the installation completes successfully.

  19. Click Discovery Center > Device Management.
  20. Click Microsoft SQL Server.
  21. Click Add new device.
    Note: Threshold based alerts are disabled by default. To manually enable threshold based alerts, go to Administration > Modules > Alerting > Alert Definitions > MS-SQL Alert definition.
  22. Select the server and collector instance where you want to store the configuration details for this device.
  23. Set these values:
    • Enter the Hostname or IP address of the SQL server.
    • Specify the Database Port and Database Instance name. For example, type Default for the SQL Server Instance name or type the named instance.
    • Specify the mode of authentication used for the SQL Server: SQL Authentication or Windows Authentication
    • If using SQL Server authentication, type the username and password for the SQL Server.
    • If using Windows authentication, provide the Windows domain, username, and password. Use either the local or domain username.
  24. Click Validate and Add to check connectivity with the SQL Server.
  25. Click OK.
  26. Click Save.