5/14/2026 3:28 PM

5/14/2026 3:40 PM

DPA uses three core components: the DPA application server, the DPA repository database, and the monitored SQL Server instance(s). DPA collects performance data from the monitored SQL Server instance(s) and stores that data in the repository database for display in the web console.

For best performance, the DPA server, repository database, and monitored database instances should be on the same high-speed LAN. Also, the repository should not be hosted on a database instance that you plan to monitor, because that can affect performance.

This document is intentionally limited to a small local lab / proof-of-concept deployment using SQL Server Express on a new VM for both the DPA application and repository. Please note that although DPA can work with SQL Server Express for the repository, SolarWinds does not officially support Express editions for the repository because of the 10 GB database size limit.

Database Performance Analyzer

Scope and assumptions

• One new Windows VM will host both:

  • the DPA application

  • the SQL Server Express repository

• You will use this to monitor SolarWinds Platform database SQL Server instance(s)

• This is intended for evaluation, lab, or very small environments only

• If you later move to production use, you should move the repository to a fully supported SQL Server edition rather than remain on SQL Express.

Minimum platform requirements

Official DPA application minimums

For 1–20 monitored database instances, the documented DPA server minimums are:

• 4 CPU cores

• 10 GB RAM

• 40 GB disk space

• Supported Windows Server or Linux OS; Windows desktop OS is evaluation only.

Repository considerations

The repository has its own sizing requirements, and for 1–20 monitored database instances, DPA requires 8 GB of database cache available for the repository. If DPA and the repository are installed on the same server, that server must meet the repository requirements in addition to the DPA application requirements.

Practical VM recommendation for this scoped deployment

For this specific SQL Express lab deployment, use at least:

• 4 vCPU

• 16 GB RAM

• 100 GB free disk

• Windows Server 2019 or 2022

• Static IP or stable hostname

• SQL Server Express 2019 or 2022

• SSMS installed for backup/export work

This is a practical recommendation for a small local deployment based on the documented minimums above, plus the fact that both the DPA application and repository will share the same VM.

Step-by-step deployment

1) Download the required software

Download the following to the new VM:

• SolarWinds DPA installer from the SolarWinds Customer Portal

• Microsoft SQL Server Express installer (From MS website)

• SQL Server Management Studio (SSMS) (From MS website)

Also keep the DPA installation and upgrade documentation available as your reference set during setup.

https://documentation.solarwinds.com/en/success_center/dpa/content/install-dpa-preflight.htm

https://documentation.solarwinds.com/en/success_center/dpa/content/dpa_installation_guide.htm

2) Build the new VM

Prepare the new VM with the specs listed above and confirm:

• The VM can resolve the SolarWinds Platform SQL Server hostname

• Firewall rules allow connectivity between the DPA VM and the SolarWinds Platform SQL Server

• The VM is on the same LAN or a low-latency path to the monitored SQL instance(s) where possible.

3) Install SQL Server Express locally for the DPA repository

Install SQL Server Express on the new VM.

Important notes:

• DPA connects to the repository over TCP/IP

• SQL Server Express does not enable TCP/IP by default, so you should enable TCP/IP in SQL Server Configuration Manager before creating the repository in DPA.

Recommended post-install actions:

• Enable TCP/IP for the SQL Express instance.

• Restart the SQL Server service.

• If using a named instance, confirm the port it is listening on.

• Confirm Windows Firewall allows the SQL port.

4) Install DPA on the same VM

Install DPA on the new VM. DPA can be installed on a physical or virtual Windows or Linux server that meets the requirements.

After installation, open the DPA web console in a browser.

5) Create the DPA repository in SQL Express

After first launch, DPA requires you to create a repository database. The repository stores the monitoring credentials and the performance data collected from monitored database instances.

In DPA:

1. Launch the repository creation wizard

2. Select SQL Server as the repository type

3. Point DPA to the local SQL Express server/instance

4. Provide the SQL login with rights to create the repository database/user

5. Complete the wizard

DPA supports repository creation through the wizard for SQL Server, Oracle, MySQL, and Azure SQL Database.

6) Register the SolarWinds Platform SQL Server instance for monitoring

Once the repository is created, register the SolarWinds Platform SQL Server database instance in DPA.

In DPA:

1. Click Register DB Instance for Monitoring.

2. Select Microsoft SQL Server.

3. Enter the SolarWinds Platform SQL Server connection details.

4. Provide the monitoring account details.

5. Complete the registration wizard.

DPA requires a monitoring user with the needed privileges to gather data from the monitored SQL Server instance.

Key points during registration:

• If SQL Server Browser is running, enter the target as Server\Instance.

• DPA monitors all databases inside the registered SQL Server instance.

• If multiple SQL Server instances exist on the SolarWinds Platform database server, each instance must be registered separately.

If preferred, DPA can either:

• Create/configure the monitoring user during registration when given a privileged SQL account, or

• Use a monitoring user that the DBA creates manually in advance.

7) Allow DPA time to populate data

After the SQL Server instance is registered:

• DPA begins monitoring immediately during the trial period.

• For the first two hours, data is shown only on the Home page.

• After two hours, the rest of the DPA pages populate normally.

8) Validate monitoring

Confirm the following:

• The SolarWinds Platform SQL Server instance shows as registered.

• Wait events and activity start appearing in DPA.

• No connection or credential validation errors are shown.

• Alerts and dashboards begin to populate after the initial collection period.

Important SQL Express limitations

Because this guide uses SQL Server Express for the repository, please keep these limits in mind:

• SQL Express is not the officially supported repository platform because of its size limits.

• In Support guidance, SQL Express is typically acceptable only for small or short-term use, and default retention can fill the repository quickly depending on activity levels.

Although this guide follows your requested SQL Express design, the documented free-database recommendation for evaluations is MySQL, not SQL Express.

How to create and share the repository dump

If Support asks for the DPA repository dump, use one of the following methods.

Option A: Create a SQL backup from SSMS

1. Open SQL Server Management Studio on the DPA VM.

2. Connect to the local SQL Express instance hosting the DPA repository.

3. Locate the DPA repository database.

4. Right-click the database and select:

   • Tasks

   • Back Up

5. Choose a Full backup.

6. Save the .bak file to a local folder.

7. Compress the backup into a .zip file if needed.

Option B: Export a copy for engineering review

If Support specifically asks for a dump/script rather than a .bak:

1. In SSMS, right-click the DPA repository database

2. Use:

   • Tasks

   • Generate Scripts

3. Export schema and/or data only if Support explicitly requests that format.

Share with SolarWinds Support

After the dump is created:

1. Upload the compressed backup or dump using the secure upload method already associated with the support case.

2. Add the following notes in the case update:

   • DPA version

   • SQL Express version

   • DPA VM hostname/IP

   • Repository database name

   • SolarWinds Platform SQL Server name and instance

   • Approximate time the issue was observed

Note:

Please treat this SQL Express design as a small evaluation or temporary deployment. If the trial is successful and you want to keep DPA in service long term, we recommend moving the repository to a supported SQL Server edition and keeping the monitored SolarWinds Platform SQL Server separate from the repository host.