Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > Database Performance Analyzer (DPA) > Database Performance Analyzer Getting Started Guide > Allocate licenses > License types

License types

Created by Melanie Boyd, last modified by Anthony.Rinaldi_ret on Mar 14, 2017

Views: 59 Votes: 0 Revisions: 4

Each database instance you monitor with SolarWinds DPA requires a license. You must buy a database instance license for each database instance you monitor. In addition, you can buy virtual machine licenses to monitor the virtual infrastructure hosting a database instance.

To purchase licenses, contact the SolarWinds sales team.

Database instance licenses

SolarWinds sells licenses by category according to the database edition they are authorized to monitor.

Category 1 licenses

  • Oracle: all editions except Standard and Express
  • Sybase: all editions except Express
  • DB2: all editions except Express
  • All Category 2 database types

Category 2 licenses

  • Oracle: Standard and Express editions (including Amazon RDS)
  • SQL Server: all editions (including Amazon RDS)
  • MySQL: all editions (including Amazon RDS and Aurora)
  • Sybase: Express edition
  • DB2: Express edition

If you run out of Category 2 licenses, you can use Category 1 licenses instead. Category 1 licenses can monitor all database types.

Azure SQL Database license

  • Azure SQL Database: all editions, including databases in elastic pools

If you run out of Azure SQL Database licenses, you can use Category 1 or Category 2 licenses instead.

VM Option licenses

  • The VM option enables the DPA virtualization feature. This license is an add-on to a Category 1 or Category 2 license.

Purchase optional VM licenses to see information related to the virtual infrastructure of database instances in the Virtualization view. You can use one license to see VM-related information for one database instance.

A VM license can be applied only to a database instance for which you purchased a database instance license.

All licenses are floating

You can register more instances than you have licenses for. On the license allocation page, assign the licenses to the instances you want to monitor.

DPA does not collect data from registered database instances that are not licensed. You can view previously collected data on those instances, however.

Licensing recommendations for clustered environments

To get the maximum value from DPA, SolarWinds recommends:

  • For SQL Server availability groups (AGs), use either of the following options:

    • Register each SQL Server instance in the cluster.

      This option is recommended if there are multiple AGs in the cluster, because it ensures that DPA does not monitor the same instance more than once. DPA monitors all activity on each instance, including primary and secondary AG activity.

      With this option, DPA does not follow AGs when they fail over. Therefore, monitoring all instances in the cluster ensures monitoring continuity when failovers occur.

    • Register the AG listener.

      Use this option if you want to monitor activity on the instance that contains the primary replica of an AG. When the AG fails over, DPA follows the listener and begins monitoring the SQL Server instance that now contains the primary replica.

      SolarWinds recommends registering only one listener per cluster unless you can ensure the primary replica of multiple AGs will not be on the same instance. If you register multiple listeners whose primary replica could be on the same instance, this results in duplicate monitoring which is not recommended.

      SQL Server logins are not automatically replicated. To enable DPA to continue monitoring after a failover, you must manually create the DPA login on all instances in the cluster. 

  • For Oracle RAC, register every instance in the cluster.

  • For Oracle RAC with Data Guard, register both environments but only monitor the primary one. If a failover occurs, simply reassign the licenses to the instances in the secondary RAC environment.

Every environment is different, so talk with your SolarWinds representative for other options.

Last modified
09:40, 14 Mar 2017