Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.

 

Home > Success Center > Database Performance Analyzer (DPA) > Database Performance Analyzer Getting Started Guide > Register database instances > Database instances DPA can monitor

Database instances DPA can monitor

Created by Melanie Boyd, last modified by Melanie Boyd on Sep 29, 2016

Views: 72 Votes: 0 Revisions: 3
DPA_GS_Home.png

DPA can monitor database instances that you manage running on physical or virtual servers. It can also monitor Amazon RDS instances hosted in the Amazon Elastic Compute Cloud (EC2). The DPA server must be able to connect to the server hosting the monitored instance.

Self-managed databases

Database Required Privileges Supported Version

Oracle

SYS user
  • 11.2.x
  • 12.1.x (single tenant and multitenant)

Microsoft SQL Server

SYSADMIN role
  • 2008 SP4
  • 2008 R2 SP3
  • 2012 SP3
  • 2014 SP2
  • 2016 SP1

SAP Sybase ASE

SA_ROLE
  • 15.5
  • 15.7
  • 16

IBM DB2 LUW

SYSADM
  • 9.5
  • 9.7
  • 10.1
  • 10.5
MySQL

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.6.10+
  • 5.7.9+
  • Percona 5.6 and 5.7

Amazon RDS databases

DPA can monitor Amazon RDS Oracle, Microsoft SQL Server, and MySQL instances. Some features that are available on self-managed database instances are not available for Amazon RDS instances, because of Amazon RDS access restrictions.

Amazon RDS Supported Versions Key Differences

Oracle

  • 11.2.x
  • 12.1.x

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.

Microsoft SQL Server

  • 2008 R2 SP3
  • 2012 SP2
  • 2014 SP1

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.

WMI-based statistics that are not available:

  • 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.
MySQL
  • 5.6.10+
  • 5.7.9+
  • Aurora 5.6.10a+
No differences

Azure databases

Database Required Privileges Supported Version
Azure SQL db_owner role
  • V12
Last modified
16:56, 29 Sep 2016

Tags

Classifications

Public