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). The server hosting DPA must be able to connect to the monitored server.

Self-managed databases

When you register a self-managed database instance, you must provide the credentials of a privileged user. The required privileges are listed below. During registration, the privileged user either creates the monitoring user, or grants privileges as needed to an existing user designated as the monitoring user. DPA does not store the credentials of the privileged user. 

Database	Privileges Required for the Privileged User	Supported Versions
Oracle	SYS user	18.3.x (single tenant and multitenant1) 12.2.x (single and multitenant) 12.1.x (single and multitenant) 11.2.x
Microsoft SQL Server	SYSADMIN role	2017 (Windows and Linux) 2016 SP2 2014 SP2 2012 SP4 2008 R2 SP3 2008 SP4
SAP Sybase ASE	SA_ROLE	16 15.7 15.5
IBM DB2 LUW	SYSADM	11.1 10.5 10.1 9.7
MySQL2	The privileged user requires the CREATE USER permission and must be able to grant the following permissions: PROCESS on *.* SELECT & UPDATE on performance_schema.* To enable the retrieval of query execution plans, this privileged user must be able to grant the following permissions: SELECT, INSERT, UPDATE, DELETE on *.*	5.7.9 5.6.10 Percona 5.6 and 5.7 Maria 10.0, 10.1, and 10.2 DPA cannot monitor MySQL 8.0 databse instances.

¹ 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.

² See Requirements for monitoring MySQL database instances with DPA.

Amazon RDS databases

DPA can monitor Amazon RDS Oracle, Microsoft SQL Server, and MySQL instances.

Amazon RDS	Supported Versions
Oracle	12.2.x 12.1.x 11.2.x
Microsoft SQL Server	2017 2016 2014 SP1 2012 SP2 2008 R2 SP3
MySQL	5.7.9+ 5.6.10+ Aurora 5.7.12+ Aurora 5.6.10a+

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.

Azure databases

Database	Required Privileges	Supported Version
Azure SQL	db_owner role	V12

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.