Documentation forDatabase Performance Analyzer

Register a single SQL Server database instance

You must register all of the database instances that you plan to monitor with DPA. You can register an individual instance using the Register Instance wizard, or you can register multiple instances.

DPA can monitor many database types, including Oracle, Sybase, Db2, PostgreSQL, MySQL, AWS, and Azure. This example shows you how to register a Microsoft SQL Server database. For information about registering other types of database instances, see Register a database instance for monitoring in the DPA Administrator Guide.

Before you start

Before you run the Register Instance wizard, make sure:

  • The database instance is a version that DPA can monitor.
  • You have credentials to a login with SYSADMIN privileges for the SQL Server database instance.

Run the wizard

  1. To open DPA, enter one of the following URLs in a web browser:
    • http://<serverName_or_IP>:8123
    • https://<serverName_or_IP>:8124

  2. If you have not registered any database instances, the Register Instance wizard opens automatically.

    If the wizard does not open automatically, click Register DB Instance for Monitoring near the top left of the DPA homepage.

  3. Complete the wizard panels as described in the following table.

Panel Instructions
Select Database Instance Type Select Microsoft SQL Server.
Enter Monitored Database Instance Connection Information

  1. Enter connection information for the SQL Server instance:

    • If the SQL Server Browser service is running, enter the server name or IP address and the instance name in this format: Server\Instance.
    • If the SQL Server instance contains one or more Availability Groups, click Note for Availability Groups for instructions on how to register primary and secondary replicas.
    • Otherwise, enter the server name or IP address and the port number.

    DPA monitors all databases within the instance. If more than one instance exists on the server, you must register each instance separately in DPA.

  2. Select the type of authentication you want to use. If Mixed Mode was selected during the SQL Server installation, you can choose either option.

  3. Enter a SYSADMIN login that DPA can use to register the instance.

    DPA does not use or store these credentials after you complete the wizard.

    • For Windows authentication, enter <DOMAIN>\<username> in the SYSADMIN User field.

    • For SQL Server authentication, enter the credentials that you enter on the Connect to Server dialog in SQL Server Management Studio (with Database Engine as the Server type).
Enter the Monitoring User

Create or specify the SQL Server or Windows account that DPA will use to gather information. To ensure that the account has the required permissions, SolarWinds recommends creating a new account.

To create a new account:

  1. Click Yes.
  2. Select SQL Server as the authentication method. (DPA cannot create a new Windows account.)
  3. Enter a user name and password for the new account, or accept the default values.

To specify an existing account:

  1. Click No.
  2. Select either authentication method.

  3. Enter the user name and password of an existing account.

    For Windows authentication, enter <DOMAIN>\<username> in the Monitoring User field.

Summary

Review the information and click Register Database Instance.
Database Instance Registration Complete Click Finish to return to the DPA homepage.

View performance data for the database instance

If you register a database instance within the 14-day trial period, DPA begins monitoring the instance immediately. After the trial period, you must activate a license to monitor the database instance.

When DPA is monitoring an instance, the homepage shows summary information about the instance.

For the first two hours after you register the instance, data is shown only on the homepage. After two hours, all DPA pages are populated.

Click the instance name to view detailed information about that instance. For more information, see Investigate a SQL statement causing long waits.