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 > DPA repository database requirements

DPA repository database requirements

Updated: July 6, 2017

The repository database stores the data collected by SolarWinds 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
  • 2008 R2 SP3
  • 2012 SP3
  • 2014 SP2
  • 2016 SP1
Azure SQL Standard Service Tier or higher V12
  • Community
  • Enterprise
  • 5.6.10 and later
  • 5.7.9 and later
  • Aurora 5.6.10a and later


  • Standard
  • Enterprise
  • 11.2
  • 12.1 (single tenant and multitenant)


  • 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 use an Amazon Relational Database Service (RDS) for MySQL or Aurora instance as a repository.
  • 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.

Repository database server

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

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
Reserved RAM 4 GB 8 GB 8 GB 16 GB
OS Architecture 64-bit
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.

Required administrator credentials

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

Repository database type Credentials
Oracle database administrator (DBA)

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.

Next steps

You can:

Last modified
10:48, 7 Jul 2017