Documentation forDatabase Performance Analyzer

Database Performance Analyzer 2019.4 Release Notes

Release date: November 5, 2019

These release notes were last updated on August 10, 2020.

These release notes describe the fixed issues in Database Performance Analyzer 2019.4 and in the DPA 2019.4.1 Service Release. They also provide information about upgrades and describe workarounds for known issues.

If you are looking for previous release notes for Database Performance Analyzer, see Previous Version documentation.

New features and improvements in DPA

DPA 2019.4 offers new features and improvements compared to previous releases of DPA.

Custom email templates for alert notifications

When an alert is triggered, DPA sends an email to notify the designated recipients. DPA 2019.4 introduces custom templates that you can use to tailor the contents of alert notification emails. You can create multiple custom email templates for different types of alerts.

Creating a custom email template requires no coding. Specify the email subject line and content by dragging and dropping variables and by entering static text.

After you create one or more custom email templates, you can designate one of your custom templates as the default template.

Additions to the REST API

The DPA REST API now includes additional endpoints that you can use to:

  • Retrieve, update, and reset values for DPA advanced options.
  • Retrieve and manage custom alert email templates.
  • Retrieve alert groups and assign or remove database instances.
  • Retrieve alerts and alert statuses, assign or remove database instances, and assign or remove an email template.
  • Create and manage custom properties that can be used in custom email templates.
  • Create and manage database groups.
  • Change the logging level for the DPA REST API.
  • Get information about vSphere servers and VMware events.

Table tuning best practices

When DPA generates a table tuning advisor, it evaluates the table and its indexes against a set of best practices. The table tuning advisor reports any violations, and DPA provides recommendations for resolving violations.

You can use DPA's advanced configuration options to customize the best practice checks for your environment.

VM co-stop metrics

For database instances that run on a virtual machine (VM), the Resources tab includes two new CPU metrics to track co-stop wait time. Co-stop wait time occurs on VMs configured to use multiple virtual CPUs (vCPUs). It measures the time that the VM is ready to execute but has to wait on vCPU resources to be freed from other VMs contending for those vCPUs.

DPA collects VM metrics only if you register the VM for monitoring. Monitoring a VM requires a VM license.

DPA provides the following co-stop metric resources:

  • VM Total Co-Stop Time is the total amount of time (in milliseconds) that the VM was ready to execute but had to wait.

  • VM Co-Stop is the percentage of time that the VM was ready to execute but had to wait.

If SQL statements are experiencing high CPU/Memory waits, check the co-stop metrics. If they are not near 0, co-stop could be contributing to the CPU/Memory waits. To reduce co-stop, you can:

  • Decrease the number of vCPUs on the VM.
  • Add additional CPUs to the pool available to the VMs.
  • Use vMotion to migrate other VMs to a different host to reduce contention.

Additional VM information on the Query Details page

For database instances that run on a VM, resource metrics charts on the Query Details page now show the following additional information:

  • VMware events are shown as annotations. Hover over a dot at the top of the chart to see the events.

  • When a VM is migrated to another host, the chart lines distinguish between the hosts.

New version numbering system

DPA now uses same version numbering system that is used by SolarWinds (Undefined variable: Core_var.Product_family). The version number consists of the four-digit year of the release followed by the quarter of the release. If there is a service release, it appears after the quarter:


Changes to system requirements

DPA 2019.4 adds support for the following versions:

Monitored database instances
  • Oracle 19
  • Oracle 18.4
  • Microsoft SQL Server 2019 (Windows and Linux)
  • MySQL 8.0
  • Percona 8.0
  • Maria 10.3
  • Azure SQL Managed Instance (ASMI) V12
Repository database versions
  • Oracle 19 (on-premises only)
  • Oracle 18.4 (on-premises only)
  • Microsoft SQL Server 2019 (Windows or Linux)

DPA 2019.4 removes support for the following versions:

Monitored database instances
  • Microsoft SQL Server 2008
Repository database version
  • Microsoft SQL Server 2012

For a complete list of supported platforms, see the DPA 2019.4 system requirements.

Fixed issues

DPA 2019.4 fixes the following issues.

Case number Description

DPA can now collect Oracle execution plans even when the plan includes a table whose name contains more than 50 characters.


Previously, when you accessed the Table Tuning Advisor page for a large table on a busy database, the Current Table Information section sometimes displayed the message "Data not retrieved" and the idc.log reported timeout errors. Performance improvements to the index analysis job and the process of retrieving table data have resolved this issue.


DPA can now monitor MySQL 8.0 databases. See the DPA 2019.4 System Requirements for details.

00280876 When you have a SQL Server repository database and the value of LOCKING-GLOBAL-SEQ in the conprm table reaches the maximum for an int data type, DPA monitoring no longer fails with error messages about data truncation.

Table tuning advisors for SQL Server database tables do not include internal server updates when determining the Last Used date for an index.


When the hostname of the DPA server starts with "ng," buttons on the Options pages, such as the User Administration button, now open the correct page.


When you are monitoring a SQL Server database instance that runs on Amazon Relational Database Service (Amazon RDS) and you open a table tuning advisor, DPA no longer displays the following message:

You are not authorized to perform this action. Contact your DPA administrator.


DPA displays line breaks in SQL statements correctly.


The query to retrieve the status of SQL Server availability groups (AGs) no longer times out in deployments with a large number of AGs, and the AG status is displayed correctly.


When DPA has been monitoring an instance for less than one day and you attempt to drill in to a chart on the Virtualization tab, DPA no longer returns a NullPointerException error. Instead, DPA displays the trend chart for the current day.

You can drill in to the chart after one day of data has been collected and summarized.

00278967, 00280076

When DPA is running on Amazon Web Services and the embedded mail server is used, DPA now displays trends charts, storage I/O, and reports as expected.


DPA now differentiates between a MySQL database instance and an Aurora MySQL database instance. For Aurora MySQL instances, it displays both the MySQL version and the Aurora engine edition.


Statistics are no longer missing from the Query Details page when the time zone for the DPA server is set using the GTM+nn:nn format.


When you are monitoring an Oracle database instance, navigating to the Blockers tab for a timeslice no longer returns an error.


DPA can register an Amazon RDS for MySQL read-only database instance for monitoring. To do so, complete the following steps:

  1. Register the corresponding read/write instance in DPA.
  2. Copy the user and permissions to the read-only instance.
  3. Edit the file and add the following setting:


  4. Use the registration wizard to register the instance:
    • For the monitoring user, choose Provide monitoring user. Then enter the credentials for the same user specified for the read/write instance.
    • On the Configuration for Monitoring panel, choose Leave As Is.

When a SQL statement was not executed during a time period, the wait time shown on the Query Detail page is consistent with the wait time shown in reports, such as the Average Wait for Single SQL report.


The message displayed when DPA cannot connect to the repository has been updated to provide more accurate information about the cause of the problem.


When a SQL Server database instance is being restored, DPA no longer stops monitoring the instance.


The IO_STATS_POLL_DB_FILE_COUNT value is updated even when the value of IO_STATS_POLL_ENABLED is AUTO_OFF. This enables DPA messages to display the correct IO_STATS_POLL_DB_FILE_COUNT value.


The SQL Server Error Log Alert now sends a notification immediately when it is triggered, even if the DPA server and the monitored SQL Server instance are in different time zones.


DPA now displays the Page Life Expectancy metric for SQL Server database instances in a NUMA (non-uniform memory access) configuration.


In certain SQL Server environments with high CPU usage, DPA no longer displays incorrect values in the Instance CPU Utilization resource metric.


For Db2 10.5 database instances, DPA no longer displays wait times with the type "NONE."


The description of the VM Ready Time metric has been updated to clarify what this value represents.


Links from DPA Central to remote DPA servers work correctly.


The performance of DPA's index analysis has been improved to avoid causing deadlocks.


The status of the primary replica in an AG is updated even If the server name for the replica is null.

DPA 2019.4.1 fixes the following issues.

Case number Description


When you are monitoring a SQL Server database instance, the trends chart on the Top Files tab now displays file names correctly.


Registering a SQL Server database instance on Amazon RDS no longer fails due to permission issues.


When the same SQL statement runs on multiple monitored database instances, DPA displays information about the statement on both instances.


When an Oracle monitored instance is registered through the TNS descriptor, email notifications are sent as expected when an alert is triggered, and there is no null pointer exception at database port field.


When you attempt to save a custom email notification template, the message "Form contains error, fix them before saving" is no longer displayed when there are no errors in the form.

New customer installation

Return to top

For information about installing DPA 2019.4, see the DPA Installation and Upgrade Guide. You can download a free trial from the SolarWinds website.

How to upgrade

If you are upgrading from a previous version, use the following resources to plan and implement your upgrade:

Known issues

Return to top

Monitoring Db2 9.7 databases

Issue: When you attempt to monitor a Db2 9.7 database instance with DPA 2019.4, monitoring does not start and no data is returned.

Resolution/Work-around: To monitor a Db2 9.7 database instance, complete the following steps:

  1. From the DPA menu, click Options.
  2. Under Administration > Configuration, click Advanced Options.
  3. Click the DB Instance Options tab, and then select the Db2 9.7 database instance from the drop-down menu.
  4. In the upper-right corner, select Support Options.

    The Edit Option dialog box opens.

  6. Enter the following in the New Value box and click Update:

    (snapshot_appl_info(CAST(NULL AS VARCHAR(1)),
    -2)) AS ai
    (snapshot_statement(CAST(NULL AS VARCHAR(1)),
    -2)) AS s ON
    s.agent_id = ai.agent_id
    (snap_get_appl_info_v95(CAST(NULL AS VARCHAR(1)),
    -2)) ai95 ON
    s.agent_id = ai95.agent_id
    AND ai.agent_id = ai95.agent_id
    s.agent_id = ai.agent_id
    AND s.stmt_type <> 4
    AND stmt_stop IS NULL
    AND ai.appl_id <> APPLICATION_ID()
    AND is_system_appl = 0
    AND ai95.agent_id = ai.agent_id
    AND ai95.agent_id = s.agent_id
    AND ai.appl_status NOT IN (0,
    stmt_start DESC,
  7. Restart DPA.


Creating the monitoring user when registering a MySQL 8.0 database instance

Issue: For MySQL 8.0, the default authentication plug-in has changed from mysql_native_password to caching_sha2_password. If you attempt to register a MySQL 8.0 instance and allow DPA to create the monitoring user, registration fails because DPA cannot authenticate a user created with the default option.


  1. Create the monitoring user manually and specify that the mysql_native_password plugin be used to authenticate that user. For example:

    CREATE USER 'userName'@'localhost' IDENTIFIED WITH mysql_native_password BY 'userPassword';

    You can verify user creation by querying the mysql.user table:

    select user,host,plugin from mysql.user;

  2. Grant the required privileges to the user. See the GRANT statements in the script available through the Register Instance Wizard.
  3. On step 2 of the Register Instance Wizard, select I'll create the database user. Then enter the user name and password of the user you created.


Adding a distributed AG to a server prevents DPA from monitoring non-distributed AGs on the server

Issue: If DPA is monitoring non-distributed SQL Server Availability Groups (AGs) on a server and you add a distributed AG to the server, DPA stops monitoring the non-distributed AGs.

Resolution/Work-around: Do not add a distributed AG to the server.


Validation of the LDAP/AD server host name fails because it doesn't match the subject of the certificate

Issue: Java validates that the host name of the LDAP server matches the LDAP certificate by checking the subjectAlternativeName's dNSName fields of the certificate. If the validation fails, you will see the following error when you are configuring DPA to use AD/LDAP:

The subject of the certificate doesn't match your AD/LDAP server.

Resolution/Work-around: Follow the instructions in this article to resolve the issue.


Real Time Sessions page

Issue: When you are monitoring an Azure SQL Managed Instance (ASMI) that is registered via the public endpoint, some of the connections are closed after three minutes. If you turn the DPA monitor off, open the Real Time Sessions page, and then refresh the page after three to four minutes, the Real Time Sessions page displays the following SQL Server exception:

The connection is closed.

Resolution/Work-around: If you experience this issue, complete the following steps to configure DPA to recreate connections every three minutes:

  1. Open the following file in a text editor:


  2. Update the value of the following parameter to 180000:

    This is the timeout for idle connections, in milliseconds.

  3. Save the file and restart DPA.


Microsoft reports incorrect metric values for SQL Server on Linux

Issue: When you monitor a SQL Server 2017 database instance that runs on a Linux server:

  • The O/S CPU Utilization resource always shows usage at 100%.
  • The Instance CPU Utilization resource always shows usage at 100%.
  • The O/S Memory Utilization resource always shows usage at 0%.

When you monitor a SQL Server 2019 database instance that runs on a Linux server:

  • The O/S CPU Utilization resource always shows usage at 100%.
  • In some cases, the Instance CPU Utilization resource always shows usage at 100%.

Microsoft reports these values.

Resolution or Workaround: Disregard the values that are incorrect on your version of SQL Server. You can also disable the collection of a metric that shows incorrect data.


Monitoring a database instance in the Oracle Public Cloud
Issue: When DPA is monitoring a database instance in the Oracle Public Cloud, it sometimes reports incorrect values.
Resolution/Work-around: DPA does not support monitoring database instances deployed in the Oracle Public Cloud. Use DPA to monitor supported database instance types.


Deprecation notices

Return to top

This version of Database Performance Analyzer deprecates the following platforms and features.

Deprecated platforms and features are still supported in the current release. However, they will be unsupported in a future release. Plan on upgrading deprecated platforms. 

Type Details
Self-managed DPA server Support for installing DPA on a self-managed Windows Server 2012 server is deprecated. Installing DPA on a Windows Server 2012 is still supported in the DPA 2019.4 release, but support will be removed in an upcoming release.
VMware DPA will be ending support for VMware vCenter Server 6.0 and VMware ESX/ESXi Host 6.0 in an upcoming release. DPA 2019.4 still supports VMware 6.0, but SolarWinds encourages users to upgrade to VMware 6.5 or 6.7 at their earliest convenience.

End of support

Return to top

This version of Database Performance Analyzer no longer supports the following platform.

Type Details
Repository database

SQL Server 2012 is no longer supported as the DPA repository database.

Monitored database instances

DPA can no longer be used to monitor SQL Server 2008 database instances.

End of life

Return to top

Version EoL Annoucement EoE Effective Date EoL Effective Date
DPA 11.0 November 5, 2019 End-of-Life (EoL) announcement - Customers on DPA version 11.0 or earlier should begin transitioning to the latest version of DPA. March 7, 2020 End-of-Engineering (EoE) - Service releases, bug fixes, workarounds, and service packs for DPA version 11.0 or earlier will no longer actively be supported by SolarWinds. March 7, 2021 End-of-Life (EoL) - SolarWinds will no longer provide technical support for DPA version 11.0 or earlier.
DPA 10.2 August 28, 2018 End-of-Life (EoL) announcement - Customers on DPA version 10.2 or earlier should begin transitioning to the latest version of DPA. November 26, 2018 End-of-Engineering (EoE) - Service releases, bug fixes, workarounds, and service packs for DPA version 10.2 or earlier will no longer actively be supported by SolarWinds. November 26, 2019 End-of-Life (EoL) - SolarWinds will no longer provide technical support for DPA version 10.2 or earlier.

See the End of Life Policy for information about SolarWinds product lifecycle phases. For supported versions and EoL announcements for all SolarWinds products, see Currently supported software versions.

Legal notices

Return to top

© 2019 SolarWinds Worldwide, LLC. All rights reserved.

This document may not be reproduced by any means nor modified, decompiled, disassembled, published or distributed, in whole or in part, or translated to any electronic medium or other means without the prior written consent of SolarWinds. All right, title, and interest in and to the software, services, and documentation are and shall remain the exclusive property of SolarWinds, its affiliates, and/or its respective licensors.


The SolarWinds, SolarWinds & Design, Orion, and THWACK trademarks are the exclusive property of SolarWinds Worldwide, LLC or its affiliates, are registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other SolarWinds trademarks, service marks, and logos may be common law marks or are registered or pending registration. All other trademarks mentioned herein are used for identification purposes only and are trademarks of (and may be registered trademarks) of their respective companies.