Submit a ticketCall us

WebinarUpcoming Webinar: How Help Desk and Remote Support Pays for Itself

Learn how help desk software can simplify ticketing management, allow you to track hardware and software assets, and accelerate the speed of IT support and service delivery. Gain insights on how remote support tools allow your IT team to maximize their efficiency and ticket resolution by expediting desktop troubleshooting, ultimately helping keep end-users happy and productive.

Register here.

Home > Success Center > Database Performance Analyzer (DPA) > DPA Documentation > Previous Versions > DPA 10.1 system requirements

DPA 10.1 system requirements


Created by Anthony.Rinaldi_ret, last modified by Melanie Boyd on Apr 23, 2018

Views: 808 Votes: 0 Revisions: 9

Updated February 2, 2016

Supports: DPA 10.1

Server requirements

You can install SolarWinds DPA on any physical or virtual Windows, UNIX, or Linux server that supports the Java Runtime Environment (JRE) 1.6, 1.7, or 1.8.

You can also launch SolarWinds DPA in the Amazon Elastic Compute Cloud (Amazon EC2) from an Amazon Machine Image (AMI). The AMI contains a SolarWinds DPA server and a built-in Microsoft SQL Server instance configured as the SolarWinds DPA repository.

Self-managed DPA server

SolarWinds DPA does not require a JRE on Windows. You must install JRE 1.6, 1.7, or 1.8 on UNIX or Linux.

Supported operating systems

  • Windows 2008
  • Windows 2008 R2
  • Windows 2012
  • Windows 2012 R2
  • Windows 8 and 8.1
  • Windows 10
  • UNIX
  • Linux

The other minimum requirements for the server specifications and operating system architecture depend on the number of database instances you plan to monitor.

Monitored database instances CPUs RAM dedicated to DPA OS architecture
1 - 20 1 1 GB 64-bit
21 - 50 2 2 GB 64-bit
51 - 100 4 4 GB 64-bit
101 - 250 4 8 GB 64-bit

More than 250 monitored instances

Do you plan to monitor more than 250 database instances? Consider using more than one SolarWinds DPA server and Link together separate DPA servers.

Amazon EC2 DPA server

The minimum required Amazon EC2 instance type for the SolarWinds DPA server AMI is m3.medium. Smaller instance types are not supported.

An m3.medium size instance can reliably monitor 10 database instances. You may need a larger instance type to reliably monitor more than 10 database instances.

Repository database requirements

The repository database stores the data collected by SolarWinds DPA. You can host the repository database on an instance of Oracle or Microsoft SQL Server:

Database Edition Version
Microsoft SQL Server Express
2008 SP4
2008 R2 SP3
2012 SP2
2014 SP1
Oracle Express
12.1 (single tenant and multitenant)

SolarWinds recommends against using Express editions of Oracle or SQL Server for the repository because of the database size limits.

Do not host the repository on a database instance that you plan to monitor, because this affects the performance of that instance.

SolarWinds DPA does not support using Amazon Relational Database Service (RDS) instances as a repository. You can host a self-managed Oracle or SQL Server database on Amazon EC2 to use as your repository.

Repository database server

If you install SolarWinds DPA on the same server as the repository database, you need these requirements in addition to the SolarWinds DPA requirements.

Monitored database instances CPUs RAM dedicated to DPA OS architecture
1 - 20 1 2 GB 64-bit
21 - 50 2 4 GB 64-bit
51 - 100 4 8 GB 64-bit
101 - 250 4 16 GB 64-bit

Adequate disk space for the repository database

The amount of disk space your repository uses is determined by the number of database instances you are monitoring and the activity level of each instance.

Database instance activity level Disk space required
Low 1 GB
Medium 3 GB
High 5 GB


You are monitoring 5 low, 3 medium, and 2 high activity database instances.

(5 x 1GB) + (3 x 3GB) + (2 x 5GB) = 24 GB

Reserve at least 24 GB to provide adequate disk space for this repository database.

Administrator credentials are required

You must know the database administrator (DBA) credentials (Oracle) or the Sysadmin credentials (SQL Server) for the database instance hosting your repository.

Database versions you can monitor

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

Self-managed databases

Database Required privileges Supported versions
Oracle SYS user


12.1 (single and multitenant)

Microsoft SQL Server SYSADMIN role

2008 SP4

2008 R2 SP3

2012 SP3


2014 SP1










MySQL SYS user



Percona 5.6

Note: DPA cannot monitor MySQL 8.0 databse instances.

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



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



No differences

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

Web browsers

SolarWinds DPA supports the following browsers:

  • Microsoft Internet Explorer 9, 10, and 11

    Do not use IE compatibility view. It may cause SolarWinds DPA to function incorrectly.

  • Mozilla Firefox: latest stable version
  • Google Chrome: latest stable version

MySQL requirements

SolarWinds recommends the following settings to optimize reporting capabilities for a MySQL database instance.

MySQL Performance Schema

The Performance Schema monitors server events and collects performance data. If the Performance Schema is not enabled, SolarWinds DPA provides limited data. Monitoring with the Performance Schema disabled excludes the following data:

  • All instrumented wait events
  • All wait operations
  • All file wait time, broken out by file
  • All object wait time, broken out by index and table
  • SQL statistics
  • Performance-schema dependent alerts

The Performance Schema must be enabled at server startup. In MySQL versions 5.6.6 and later, the Performance Schema is enabled by default.

Global and Thread Instrumentation

Global Instrumentation and Thread Instrumentation must be enabled in the Performance Schema configuration. Disabling these instruments has the same effect as disabling the Performance Schema.

By default, SolarWinds DPA enables these instruments in the configuration. However, if you select the Leave As Is option for Performance Schema setup, you must verify that Global Instrumentation and Thread Instrumentation are enabled in the existing Performance Schema configuration.

show_compatibility_56 system variable

If the monitored database instance is MySQL 5.7.6 or later, SolarWinds recommends turning on the show_compatibility_56 system variable. If this variable is on, SolarWinds DPA can collect data for all metrics.

If this variable is off and the Performance Schema is enabled, SolarWinds DPA cannot collect data for the following metrics:

  • Selects
  • Inserts
  • Updates
  • Deletes
Last modified