Submit a ticketCall us

Putting Your Logs Where They Belong with the New SolarWinds Log Manager for Orion

The new SolarWinds® Log Manager for Orion® finally puts your log data right where it belongs, in the heart of your Orion console. Gain insight into the performance of your infrastructure by monitoring your logs in a unified console allowing you to see a wealth of information about the health and performance of your network and servers.

Reserve a Seat for Wednesday May 23rd 11am CDT | Reserve a Seat for Tuesday May 22nd 10:30am GMT | Reserve a Seat for Tuesday May 22nd 1pm SGT / 3pm AEST

Home > Success Center > Database Performance Analyzer (DPA) > DPA 11.1 Administrator Guide > Register a database instance for monitoring > Register an Azure SQL database

Register an Azure SQL database

Created by Anthony.Rinaldi_ret, last modified by Anthony.Rinaldi_ret on Feb 20, 2017

Views: 192 Votes: 0 Revisions: 2

To register multiple Azure SQL databases using the Mass Registration feature, follow the instructions in this KB article.

To register a single Azure SQL database for DPA to monitor:

  1. On the DPA home page, click Register DB Instance for Monitoring.
  2. Under Azure, click Azure SQL DB.
  3. Click Next.
  4. Complete the wizard panels as described in the following table.
Panel Instructions
Enter Monitored Database Instance Connection Information

Enter the server name, port, and database name. You cannot use an IP address in the Server Name field.

Choose a method for creating or configuring the monitoring user.

To create a new account:

  1. Click Let DPA create a new contained user or configure an existing contained user for me.
  2. Enter the credentials of an existing user with privileges to create the monitoring user and to grant the required permissions.

    The privileged user must be a member of the db_owner role.

    The credentials for the privileged user are not used or stored after the registration.

To specify an existing account:

  1. Click I'll create the database user.
  2. Enter credentials. DPA encrypts the password.

Alternatively, you can use the script that DPA provides to create a monitoring user.

  1. Click Monitoring User Creation Script, and follow the on-screen instructions.
  2. Copy and run the edited script on your Azure SQL database.
  3. Provide this user as your monitoring user.
Enter the Monitoring User

DPA gathers information through this user from the monitored database. You can create a monitoring user through DPA or use an existing user, such as for read-only replica databases.

To register a read-only geo-replica, you must create a monitoring account through the primary server first.

SolarWinds recommends creating a new account because DPA requires special permissions that existing users may not have.

To create a new account:

  1. Click Let DPA create a new contained user.
  2. Enter credentials.

To specify an existing account:

  1. Run the following SQL statement on the Azure SQL database:
    ALTER ROLE db_owner ADD member <USERNAME>;
  2. Click Let DPA configure an existing contained user.
  3. Enter credentials.
Oracle Repository Tablespace

If your repository database is not Oracle, the wizard skips this step.

Choose the tablespace in the repository database to store DPA performance data for this monitored instance.

By default, the performance data is stored in the default tablespace of the repository user. However, data for monitored instances can be stored in separate tablespaces.

Select the Alert Groups

If you have no Alert Groups set up, or if this new database instance does not match the database type of the Alert Group, the wizard skips this step.

Alert Groups simplify alert configuration and help make alerting more consistent across the monitored database instances.

Select the Alert Groups you want the new database instance to join.

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

Enable deadlocks for read-only geo-replicas

To enable the deadlock feature for read-only geo-replica Azure SQL databases, you must create and enable an Extended Event Session (EES).

If you registered the primary server first, an EES is already created and synced. Skip to step 2.

Otherwise, connect to the primary server first to create an EES.

  1. Run the following SQL statement:
    CREATE EVENT SESSION [dpa_deadlock_capture] ON DATABASE
    ADD EVENT sqlserver.xml_deadlock_report
    ADD TARGET package0.ring_buffer(SET max_events_limit=(1000), max_memory=(256))
    -- ALTER EVENT SESSION [dpa_deadlock_capture] ON DATABASE STATE = START;
  2. Connect to the read-only replica database.
  3. Click Extended Events > Sessions.
  4. Enable the dpa_deadlock_capture session.
Last modified