Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
Register Now.

Home > Success Center > Database Performance Analyzer (DPA) > DPA 11.0 Installation Guide > DPA requirements > Database versions you can monitor

Database versions you can monitor

Updated: July 6, 2017

SolarWinds 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). You can monitor Oracle, Microsoft SQL Server, Azure SQL, MySQL, SAP ASE, and IBM DB2 database instances. The server hosting DPA must be able to connect to the monitored server.

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. Access to objects may be limited. 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 no SYSADMIN role: DPA user is a member of PROCESSADMIN role.
Deadlock polling: The monitoring user and 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

Repoint database instances

If you transfer a registered Oracle or SQL Server database instance between Amazon RDS and a self-managed database, DPA historical data is not retained. An Oracle or SQL Server database instance transferred between Amazon RDS and a self-managed instance opens as a separate instance.

MySQL database instances can be repointed. You can continue monitoring where you left off after transferring a database instance between Amazon RDS and self-managed. To repoint, update the connection details of the registered database to point to the new location.

Azure databases

Database Required Privileges Supported Version
Azure SQL

db_owner role

Credentials of a user that is a member of the db_owner role are required for DPA to create the monitoring user. Alternatively, you can create the monitoring user yourself, or use the script that DPA provides to create a monitoring user.

V12

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

Next steps

You can:

Last modified
11:27, 7 Jul 2017

Tags

Classifications

Public