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 Database and Azure SQL Managed Instances. The server hosting DPA must be able to connect to the monitored instance.
If a database version is no longer supported by the vendor, DPA ceases support for monitoring that version. Monitoring these versions may continue to function; however, SolarWinds does not provide support for any issues specific to an unsupported version.
Self-managed
For information about the privileges required for the privileged user, see the instructions for registering each database type.
| Database type | Supported versions |
|---|---|
|
Oracle |
|
|
Microsoft SQL Server |
DPA supports the latest SP unless otherwise noted. |
|
SAP ASE (Sybase) |
|
|
IBM Db2 |
|
| MySQL2 |
|
| Percona2 |
|
| MariaDB2 |
|
| PostgreSQL |
|
| EDB Postgres |
|
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
Amazon RDS
DPA can monitor the following Amazon RDS database instances.
| Database type | Supported versions |
|---|---|
|
Amazon RDS for Oracle |
|
|
Amazon RDS for SQL Server |
|
| Amazon RDS for MySQL |
|
| Amazon RDS for PostgreSQL |
|
| Amazon RDS for PostgreSQL EDB |
|
Key differences for Amazon RDS for Oracle
Because of Amazon RDS access restrictions, some features that are available on Oracle self-managed database instances are not available for Amazon RDS for Oracle 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 |
|
Key differences for Amazon RDS for SQL Server
Because of Amazon RDS access restrictions, some features that are available on SQL Server self-managed database instances are not available for Amazon RDS for SQL Server instances.
| Category | Details |
|---|---|
| Unavailable alerts |
|
| 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 |
|
| 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
DPA can monitor the following Amazon Aurora database instances.
| Database type | Supported versions |
|---|---|
| Amazon Aurora for MySQL-compatible |
|
| Amazon Aurora for PostgreSQL-compatible |
|
Microsoft Azure
| Database type | Required privileges | Supported versions |
|---|---|---|
| Azure SQL Database | db_owner role |
V12 |
| Azure Database for PostgreSQL - Flexible Server |
|
|
| Azure Database for MySQL - Single Server |
|
|
| Azure Database for MySQL - Flexible Server |
|
|
| Azure Database for MariaDB |
|
|
| Azure SQL Managed Instance (ASMI) | SYSADMIN role | V12 |
Key differences between self-managed SQL Server and Azure SQL Database
| Category | Details |
|---|---|
| Unavailable Alerts |
|
| Unavailable CPU Metrics |
|
| Unavailable Memory Metrics |
|
| Unavailable Disk Metrics |
|
| Unavailable Sessions Metrics |
|
| Unavailable License Compliance Metrics |
|
| Additional DTU metrics |
|
| Additional Memory metrics |
|
| Additional Disk metrics |
|
| Additional Sessions metrics |
|
Key differences between self-managed SQL Server and ASMIs
| Category | Details |
|---|---|
| Unavailable CPU metrics |
|
| Unavailable Disk metrics |
|
| Unavailable Memory metric |
|
| Additional Disk metrics |
|
| Additional Memory metric |
|
| Additional Sessions metrics |
|
About repointing database instances
Repointing database instances is not possible between an Azure SQL Database and a SQL Server database instance.
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.
Google Cloud SQL
| Database type | Supported versions |
|---|---|
| Cloud SQL for PostgreSQL |
|
| Cloud SQL for SQL Server |
|
| Cloud SQL for MySQL |
|