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) > Key differences in monitoring Amazon RDS through DPA

Key differences in monitoring Amazon RDS through DPA

Table of contents
Created by Riggs Clough, last modified by MindTouch on Jun 23, 2016

Views: 161 Votes: 1 Revisions: 4

Updated June 13, 2016


This article overviews what the key differences are when using DPA to monitor Amazon RDS instances.



DPA version 9.1 and later


Amazon RDS Supported Versions Key Differences



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 SP4

2008 R2 SP3

2012 SP3


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 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 the processadmin role

5.6.10 and later


No differences


You can repoint MySQL but not Oracle or Microsoft SQL Server Instances

It is not possible to transfer a registered Oracle or Microsoft SQL Server database instance between Amazon RDS and a self-managed database, and retain SolarWinds DPA historical data. Any Oracle or Microsoft SQL Server database instance transferred between Amazon RDS and a self-managed instance opens as seperate instances.

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.



Last modified
19:15, 22 Jun 2016