Documentation forDatabase Performance Analyzer

Database instances DPA can monitor

DPA can monitor database instances you manage on both physical and virtual servers or Amazon RDS instances hosted in the Amazon Elastic Compute Cloud (EC2). DPA can also monitor Azure SQL and Azure SQL Managed Instances. The server hosting DPA must be able to connect to the monitored instance.

Self-managed database instances

For information about the privileges required for the privileged user, see the instructions for registering each database type.

Database type Supported versions

Oracle

  • 19 (single tenant and multitenant1)
  • 18.4 (single tenant and multitenant)
  • 12.2 (single and multitenant)
  • 12.1 (single and multitenant)
  • 11.2

Microsoft SQL Server

  • 2019 (Windows and Linux)
  • 2017 (Windows and Linux)
  • 2016
  • 2014
  • 2012

DPA supports the latest SP unless otherwise noted.

SAP ASE (Sybase)

  • 16
  • 15.7
  • 15.5

IBM Db2

  • 11.1
  • 10.5
  • 10.1
  • 9.7
MySQL2
  • 8.0
  • 5.7
  • 5.6
Percona2
  • 8.0
  • 5.7
  • 5.6
MariaDB2
  • 10.4
  • 10.3
  • 10.2
  • 10.1
  • 10.0
PostgreSQL or EDB Postgres
  • 12.x
  • 11.x
  • 10.x
  • 9.6

1 To monitor an Oracle multitenant container database (CDB), register each pluggable database (PDB) contained in the CDB. Register each PDB just as you would register an Oracle single tenant database. For more information, see Registration and licensing options for clustered environments.

2 See Requirements for monitoring MySQL database instances with DPA.

Amazon RDS database instances

DPA can monitor the following Amazon RDS database instances.

Database type Supported versions

Oracle

  • 19.0
  • 18.0
  • 12.2
  • 12.1
  • 11.2

Microsoft SQL Server

  • 2017
  • 2016
  • 2014 SP1
  • 2012 SP2
MySQL or MariaDB
  • 5.7
  • 5.6
PostgreSQL
  • 11.x
  • 10.x
  • 9.6

Key differences for Oracle databases on Amazon RDS

Because of Amazon RDS access restrictions, some features that are available on Oracle self-managed database instances are not available for Amazon RDS instances.

Category Details
Unavailable alerts Oracle Alert Log Error uses V$DIAG_ALERT_EXT instead of X$DBGALERTEXT.
Explain plans Explain plans cannot be generated with a SYS account. You must specify a different account to generate the live plan.
Workarounds for not having a SYS.UTL_CON package
  • To kill a real time session, use RDSADMIN.RDSADMIN_UTIL.KILL.
  • Trace session permissions granted through START_TRACE_IN_SESSION and STOP_TRACE_IN_SESSION.

Key differences for SQL Server databases on Amazon RDS

Because of Amazon RDS access restrictions, some features that are available on SQL Server self-managed database instances are not available for Amazon RDS instances.

Category Details
Unavailable alerts
  • SQL Server Windows Service Not Running
  • SQL Server Long Running Jobs
  • SQL Server Log Has Many Virtual Logs
  • SQL Server Job Failure
  • SQL Server Error Log Alert
Explain plans The DPA monitoring user does not have a sysadmin role and may have limited access to objects. You can specify a different user to generate the live plan before you generate the plan.
Unavailable metrics
  • CPU Queue Length
  • CPU Utilization
  • Disk Queue Length
  • Memory Paging Rate
  • Memory Utilization
  • Physical I/O Rate
  • Physical Read Rate
  • Physical Write Rate
Workaround for not having a SYSADMIN role DPA user is a member of PROCESSADMIN role
Deadlock polling The monitoring user and database administrator (DBA) do not have permission to create a custom Extended Events Session. Only the default system_health Extended Events Session can be used for deadlock polling.

About repointing database instances

You cannot transfer a registered Oracle or SQL Server database instance between Amazon RDS and a self-managed database and retain DPA historical data. An Oracle or SQL Server database instance transferred between Amazon RDS and a self-managed instance must be registered in DPA as a separate instance.

MySQL database instances can be repointed. After you transfer a MySQL database instance between Amazon RDS and self-managed, you can repoint DPA to the new instance and continue monitoring where you left off. To repoint, use the Update Connection Info wizard in DPA to update the connection details of the registered database instance to point to the new location.

Amazon Aurora database instances

DPA can monitor the following Amazon Aurora database instances.

Database type Supported versions
MySQL-compatible
  • Aurora 5.7
  • Aurora 5.6
PostgreSQL-compatible
  • Aurora 11.x
  • Aurora 10.x
  • Aurora 9.6

Azure SQL database instances

Database type Required privileges Supported versions
Azure SQL db_owner role

V12

PostgreSQL

N/A

  • 11.x
  • 10.x
  • 9.6

Key differences between self-managed SQL Server and Azure SQL database instances

Category Details
Unavailable Alerts
  • Transaction Log Freespace
  • Windows Service Not Running – SQL Server
  • SQL Server Abnormal Mirroring Status
  • SQL Server Error Log Alerts
  • SQL Server Job Failure
  • SQL Server Log has Many Virtual Logs
  • SQL Server Long Running Jobs
Unavailable CPU Metrics
  • Signal Waits
  • O/S CPU Utilization
Unavailable Memory Metrics
  • Page Life Expectancy
  • O/S Memory Utilization
  • Plan Cache Size
  • Buffer Cache Size
  • Plan Cache Hit Ratio
  • Buffer Cache Hit Ratio
  • Log Bytes Flushed
  • Log Flushes
  • SQL Compilation
  • SQL Re-Compilations
Unavailable Disk Metrics
  • Total I/O Wait Time
  • Total Read I/O Wait Time
  • Total Write I/O Wait Time
  • O/S Disk Queue Length
  • Page Reads
  • Page Writes
  • SQL Disk Read Latency
  • SQL Disk Write Latency
Unavailable Sessions Metrics
  • Transaction Rate
  • Batch Requests
Unavailable License Compliance Metrics
  • Core Count
Additional DTU metrics
  • DTU Utilization
  • DTU Consumption
  • DTU Limit
Additional Memory metrics
  • Memory Usage Utilization
  • XTP Storage Utilization
Additional Disk metrics
  • Data I/O Utilization
  • Log Write Utilization
  • Database Storage Consumption
  • Database Size
Additional Sessions metrics
  • Max Worker Utilization
  • Max Session Utilization

About repointing database instances

Repointing database instances is not possible between Azure SQL and SQL Server.

Azure SQL Managed Instance

Database type Required privileges Supported version
Azure SQL Managed Instance (ASMI) SYSADMIN role V12

Key differences between self-managed SQL Server and ASMIs

Category Details
Unavailable CPU metrics
  • CPU Queue Length
  • Instance CPU Utilization
Unavailable Disk metrics
  • Physical Read Rate
  • Physical Write Rate
  • Physical I/O Rate
  • O/S Disk Queue Length via WMI
Unavailable Memory metric
  • Memory Paging Rate
Additional Disk metrics
  • Data I/O Utilization
  • Log Write Utilization
Additional Memory metric
  • XTP Storage Utilization
Additional Sessions metrics
  • Max Worker Utilization
  • Max Session Utilization

About repointing database instances

You can repoint a self-managed SQL Server instance to an ASMI. You can use this feature if you are migrating an existing self-managed SQL Server to an ASMI and you want to have DPA data collected from both the self-managed SQL Server and the ASMI associated with the same instance in DPA. However, be aware that ASMIs have different metrics and wait types than SQL Server database instances. Because of these differences, some historical data from the SQL Server database instance will not be displayed after it is repointed to an ASMI.

To retain all data, SolarWinds recommends registering the ASMI as a new instance and reassigning the license from the SQL Server instance. You will still be able to view historical data from the unlicensed SQL Server instance.

You cannot repoint an ASMI to a self-managed SQL Server instance.