Submit a ticketCall us

Bridging the ITSM Divide
Integrated help desk and remote support software for faster resolution

Join us on Wednesday, November 29, 2017 at 11 a.m. CT, as we discuss the benefits of effectively integrating your help desk software with remote support solutions to help increase the efficiency of IT administration, improve communication, and decrease mean time to resolution (MTTR) for IT issues of all sizes. This directly impacts end-user satisfaction and your business’ bottom line. Register Now.

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: 226 Votes: 0 Revisions: 3
DPA_GS_Home.png

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). 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
  • 11.2.x
  • 12.1.x (single and multitenant)
  • 12.2 (single and multitenant)
Microsoft SQL Server SYSADMIN role
  • 2008 SP4
  • 2008 R2 SP3
  • 2012 SP3
  • 2014 SP2
  • 2016 SP1
  • 2017 (Windows and Linux)
SAP Sybase ASE SA_ROLE
  • 15.5
  • 15.7
  • 16
IBM DB2 LUW SYSADM
  • 9.7
  • 10.1
  • 10.5
  • 11.1
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
  • MariaDB 10.0, 10.1, and 10.2

Amazon RDS databases

SolarWinds 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
  • 12.2.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_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
  • 2016

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

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

After transferring 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 Privleges Supported Version
Azure SQL db_owner role
  • V12

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

Last modified

Tags

Classifications

Public