Documentation forDatabase Performance Analyzer

DPA 2020.2 System Requirements

Release date: June 4, 2020

See the following sections for minimum supported system requirements:

For information about the database instances you can register for monitoring, see Database instances DPA can monitor.

DPA Integration Module (DPAIM) compatibility

If you are not monitoring PostgreSQL database instances, DPA 2020.2.1 is fully compatible with DPAIM 11.1 or later.

If you are monitoring PostgreSQL database instances, DPAIM 2019.4 and earlier versions do not display complete information about your PostgreSQL database instances. Upgrade to DPAIM 2020.2 to display all available data from PostgreSQL instances.

Port requirements

Review and open ports on the DPA server to support communication to and from DPA.

No additional ports are required for DPA Central.

Port Protocol Service/Process Direction Encryption Description
8123 HTTP

Windows: Ignite PI Service

Linux: Java/Tomcat

Bidirectional

Default HTTP port for web server
8124 HTTPS

Windows: Ignite PI Service

Linux: Java/Tomcat

Bidirectional

TLS 1.1
TLS 1.2
TLS 1.3

Default HTTPS port for web server
8127 TCP

Windows: Ignite PI Service

Linux: Java/Tomcat

Inbound Internal Tomcat shutdown port
80 HTTP

Windows: Ignite PI Service

Linux: Java/Tomcat

Bidirectional

Default HTTP port for web server (Amazon Machine Images and Azure cloud images only)
443 HTTPS

Windows: Ignite PI Service

Linux: Java/Tomcat

Bidirectional

TLS 1.1
TLS 1.2
TLS 1.3

Default HTTPS port for web server (Amazon Machine Images and Azure cloud images only)

DPA server requirements

You can install SolarWinds DPA on any physical or virtual Windows or Linux server that supports the Java Runtime Environment (JRE) version 11.

You can also launch DPA in the cloud:

  • In the Amazon Web Services (AWS) Marketplace from an Amazon Machine Image (AMI).
  • In the Azure Marketplace.
    • The DPA virtual machine contains a DPA server on Windows and a built-in Microsoft SQL Server database instance configured as the DPA repository.
    • Individual licenses must be purchased.

Self-managed DPA server requirements

The CPU, RAM, and disk space requirements depend on the number of database instances you plan to monitor.

If you register VMware, increase the CPU and RAM requirements by 50%.

These are estimates. They are based on testing done with an average of 2-3 active sessions per monitored instance. If you are monitoring busy instances with an average of more than 2-3 active sessions, please adjust accordingly.

Hardware / Software 1 - 20 Monitored DB Instances 21 - 50 Monitored DB Instances 51 - 100 Monitored DB Instances 101 - 250 Monitored DB Instances*
CPUs 1 2 4 4
RAM dedicated to DPA 1 GB 2 GB 4 GB 8 GB
Disk space

2 GB minimum
4 GB recommended

Operating System
  • Windows Server 2019
  • Windows Server 2016
  • Windows Server 2012 R2
  • Windows 10 (evaluation only)
  • Linux
Operating System Architecture 64-bit
Character sets To support a multibyte language, the DPA server, repository, and monitored instances must be configured with the same character set.

* If you plan to monitor more than 250 database instances, consider using more than one DPA server and linking the servers together.

Requirements for an AWS DPA server

The minimum required AWS instance type for the DPA server AMI is t2.medium. Smaller instance types are not supported.

A t2.medium size instance is typically powerful enough to monitor 20 database instances. You might need a larger instance type to reliably monitor more than 20 database instances.

Requirements for an Azure DPA server

SolarWinds recommends two or more database throughput units (DTUs) per monitored database instance. See the Azure SQL Database DTU Calculator for more information.

The minimum required Azure tier is A2.

DPA repository database requirements

The repository database stores the data collected by DPA. A supported database instance must be installed on the database server.

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

Supported database versions

Database Edition Version

Microsoft SQL Server

  • Standard
  • Enterprise
  • 2019 (Windows or Linux)
  • 2017 (Windows or Linux)
  • 2016
  • 2014

The latest Service Pack is supported unless otherwise noted.

Azure SQL Standard Service Tier or higher V12
MySQL
  • Community
  • Enterprise
  • 5.7
  • 5.6
  • Amazon RDS for MySQL 5.7
  • Amazon RDS for MySQL 5.6
  • Aurora 2.03 (compatible with MySQL 5.7)

MySQL 8.0 is not supported for use as a DPA repository.

Oracle

  • Standard
  • Enterprise
  • 19 (single tenant and multitenant)
  • 18.4 (single tenant and multitenant)
  • 12.2 (single tenant and multitenant)
  • 12.1 (single tenant and multitenant)
  • 11.2

Notes:

  • Although DPA will work with the Express editions of Oracle and SQL Server, SolarWinds does not officially support these editions for the repository because of the database size limits. If you need a free database for an evaluation, SolarWinds recommends using a MySQL database.
  • You can host a self-managed Oracle, SQL Server, or MySQL database on Amazon EC2 to use as your repository.
  • If you choose Azure SQL as your repository, SolarWinds recommends two or more database throughput units (DTU) per monitored database instance. See the Azure SQL Database DTU Calculator for more information.

Self-managed repository database server requirements

If you install DPA on the same server as the repository database, the server must meet these requirements in addition to the DPA server requirements. If you register VMware, increase the CPU and RAM requirements by 50%.

These are estimates. They are based on testing done with an average of 2-3 active sessions per monitored instance. If you are monitoring busy instances with an average of more than 2-3 active sessions, please adjust accordingly.

Hardware / Software 1 - 20 Monitored DB Instances 21 - 50 Monitored DB Instances 51 - 100 Monitored DB Instances 101 - 250 Monitored DB Instances
CPUs 2 2 4 4
Database cache available for DPA 4 GB 8 GB 8 GB 16 GB
Disk space

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:

  • Low: 1 GB
  • Medium: 3 GB
  • High: 5 GB

Example: You are monitoring five low, three medium, and two high activity database instances.

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

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

Repository scalability depends on many things, including the database vendor and configuration, the specifications of the repository server, other activity on the repository server, and the activity levels of the monitored database instances.

Requirements for an AWS DPA repository database server

The following RDS instance types are recommended for AWS deployments.

Hardware / Software 1 - 20 Monitored DB Instances 21 - 50 Monitored DB Instances 51 - 100 Monitored DB Instances 101 - 250 Monitored DB Instances
RDS instance type db.m5.large db.m5.large db.m5.xlarge db.m5.xlarge
CPUs 2 2 4 4
Database cache available for DPA 8 GB 8 GB 16 GB 16 GB

Required administrator credentials

You must know the following credentials for the database instance hosting your DPA repository.

Repository database type Credentials
SQL Server SYSADMIN
Oracle database administrator (DBA)
MySQL

repository administrator

Alternatively, you can:

  • Provide the credentials of a user with privileges to create the repository user. The privileged user requires the Create, Drop, and Create User permissions and must be able to grant the following permissions:

    GRANT ALL PRIVILEGES on <databaseName>

    Where <databaseName> is the repository database you create or select when you set up the MySQL repository storage.

  • Run a script to create the repository user.
Azure SQL Database

repository administrator

Alternatively, you can:

  • Provide the credentials of a user with privileges to create the repository user. This user must be a member of the db_owner role.

  • Run a script to create the repository user.

Virtual environment requirements

In a virtual environment, DPA can remotely connect to the following to monitor the virtual environment that virtualized database instances are running on. The virtualized database instances must be registered separately from the virtual environment.

Software Version
VMware vCenter Server
  • 6.7
  • 6.5
  • 6
VMware ESX/ESXi Host
  • 6.7
  • 6.5
  • 6

Web browsers

You can use the following browsers to access the DPA web interface:

You can use the following browsers to access the DPA web interface:

  • Microsoft Edge
  • Microsoft Internet Explorer 11

    Do not use IE compatibility view. It can cause 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, 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 Instrumentation 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, 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, DPA can collect data for all metrics.

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

  • Selects
  • Inserts
  • Updates
  • Deletes

Java requirements

DPA ships with JDK 14 for Windows and Linux and installs this version of Java on the DPA server. If you are installing DPA on a supported operating system, no action is required.

For unsupported operating systems, ensure that JDK 14 is installed on the DPA server. If you need to upgrade the JDK:

  1. Download and install JDK 14.
  2. Remove old Java information by deleting the cat.txt and cat.end files from the following directory:

    <DPA_Home>/iwc/tomcat/ignite_config/

  3. At a command line, go to the DPA installation directory.
  4. Enter the following command:

    ./startup.sh