DPA 2025.4 release notes
Release date: November 18, 2025
Here's what's new in DPA 2025.4. You can find the applicable system requirements here.
To view release notes, system requirements, and product guide PDFs for supported versions of DPA, see DPA previous versions. To view release notes for multiple versions
New features and improvements in DPA
Platform Connect accounts
When you configure Platform Connect to send data to SolarWinds Observability Self-Hosted, your SolarWinds Observability account no longer expires periodically. This account expiration date is automatically extended to the DPA DBSH or DBSHDS license expiration date.
DPA Central improvements
Because of the significant improvements to DPA Central, all DPA servers must be upgraded to 2025.4 in order to integrate with DPA Central 2025.4.
DPA Central includes the following improvements:
-
View of all instances.
In previous versions, DPA Central displayed information about instances with active alerts or advisors. The My DB Instances tab has been added to display information about all database instances that the logged in user has rights to view. The information on this page is similar to the DPA Home page, including whether the instance is on or off, the database type, and whether alerts or advisors have been issued.
-
Increased scalability.
DPA Central now allows you to view information about thousands of monitored instances (up to 250,000) across multiple DPA servers.
The interval for retrieving information from other DPA servers to DPA Central is one minute. If necessary, you can increase the default refresh rate by updating the CENTRAL_CACHE_REFRESH_FREQUENCY advanced option.
When there are a large number of monitored instances, pagination is implemented to improve performance. You can choose the number of instances listed on each page.
-
Filtering and grouping.
You can filter or group instances to help you quickly locate the ones you want to see. In addition to the default filters, you can filter by any custom properties you have configured. Grouping in DPA Central is similar to grouping on the DPA Home page.
-
Configurable columns.
You can choose which columns to show or hide on the DB Instances in Alarm and My DB Instances tabs. Columns that display custom property values are available.
-
SAML authentication support
Users can now log in to DPA Central with SAML authentication to see data from all remote DPA servers. The DPA Central server and all remote DPA servers must be configured with same identity provider.
TempDB information in Real-Time Sessions
In SQL Server, the tempDB database is a system database that implicitly stores temporary data such as temporary user objects. Excessive use of the tempDB database can disrupt queries and lead to performance bottlenecks.
To help you monitor how tempDB resources are used, the following columns are available on the Sessions tab in the Real Time Sessions view. This data is available for self-managed, Amazon RDS, and Google Cloud Platform SQL Server instances that are version 2016 and later.
-
tempdb_user_obj_mb: Shows the space (in MB) currently consumed by user objects in tempDB for each session.User objects are temporary objects explicitly created by users. They include temporary tables and indexes, temporary stored procedures, table variables, and cursors.
-
tempdb_int_obj_mb: Shows the space (in MB) currently consumed by internal objects in tempDB for each session.Internal objects are created by SQL Server to process queries. For example, internal objects can be used for spooling operations, for sort space, or for hash tables. Queries that process large amounts of data can increase the space required for internal objects in tempDB.
Data is provided per session, which helps you quickly identify high tempDB consumers. To find the highest consumers, you can sort the table by the values in these columns.
To access these columns
-
From the DPA Home page, click the instance name of a SQL Server instance. The Trends tab displays information about that instance.
-
In the top-right corner, click the Current tab.
-
In the Currently Active Sessions box, click Show active sessions.
-
On the Sessions tab, scroll to the right to see the
tempdb_user_obj_mbandtempdb_int_obj_mbcolumns.
About negative numbers
In some cases, these columns might contain negative numbers. This happens because the numbers are as allocations – deallocations from Dynamic Management View (DMV) counters.
In certain situations, SQL Server’s internal operations (such as parallel execution, nested queries, or temp table cleanup) can lead to temporary over-deallocation due to timing differences or race conditions when the DMV counters are updated.
As a result, the calculated value could temporarily appear negative, even though the actual space usage is never negative.
This is a known behavior in SQL Server DMV reporting, and it does not indicate data corruption or an actual error. The values usually normalize on subsequent queries.
AI Query Assist updates
-
The AI Query Assist feature is now supported for Oracle monitored instances. In previous versions, this feature was available only for SQL Server instances.
-
You can now access the AI Query Assist option from the list of query advisors in the Tuning tab.
Improvements to the Database Instance Availability alert
The timing of the Database Instance Availability alert now works as expected, based on the execution interval specified in the alert definition.
By default, the alert is now triggered the first time DPA is unable to connect to the monitored instance (the default number of retries is 0). If you would like the alert to be triggered only after multiple consecutive connection attempts fail, set the advanced configuration option ALERT_CONNECTION_ATTEMPTS.
If you are upgrading and previously set the ALERT_CONNECTION_ATTEMPTS option, your specification is not changed.
Additional metrics collected from Azure SQL, SQL Server, and ASMI instances
DPA now collects the following additional metrics from Azure SQL, SQL Server, and Azure SQL Managed Instance (ASMI) instances.
Metrics added for Azure SQL instances
| Metric | Description |
|---|---|
| Core Count |
The number of cores used by the instance. Use this value to assess computing capacity and scaling. |
| Instance CPU Utilization |
The CPU being used for this specific SQL Server instance. This is a subset of the CPU Utilization metric. High values could indicate performance bottlenecks. |
| Page Reads |
The number of physical reads from disk to memory. High values (or spikes) could indicate insufficient storage performance, insufficient indexing, or not enough memory. |
| Page Writes |
The number of physical writes from memory to disk. This value can help you diagnose disk I/O pressure. |
| Buffer Cache Size |
The current size of the SQL Server buffer cache. |
| Log Bytes Flushed |
The number of bytes of log data being flushed per second. High values could indicate frequent transaction commits. |
| Page Life Expectancy |
The number of seconds a page stays in the buffer pool without references before it is flushed. A lower value (for example, under 300) indicates the buffer pool is under memory pressure and you should add more memory to the system or find the process in Task Manager that is consuming memory outside of SQL Server. |
| Plan Cache Size |
The current size of the SQL Server Plan Cache. This value can help you assess query plan reuse and memory usage. |
| SQL Compilations |
The number of compilations performed by SQL Server per second. Compilations are a natural part of SQL Server operations but do use CPU and other resources. Compare this to the Batch Requests/sec metric to understand if this metric is too high. Minimizing compilations will help overall performance. |
| SQL Re-Compilations |
The number of query re-compilations performed by SQL Server per second. Re-compilations occur for many reasons but this number should typically be low. High values could indicate schema changes. |
| Instance Memory Utilization |
The memory usage of the database instance. Monitor this value for memory saturation or leaks. |
| Batch Requests |
The number of batches being executed by SQL Server every second. This value indicates workload intensity and is useful for capacity planning. |
| Transaction Rate |
The number of transactions being executed every second in this instance. This value helps you identify transaction throughput and bottlenecks. |
| TempDB % Free Space |
The percentage of unused space in tempDB. If tempDB fills up and cannot autogrow, the performance of all queries will be affected as they wait for access to tempDB. |
| TempDB Free Space |
The amount of unused space in tempDB. |
| TempDB Size |
The amount of space currently allocated for tempDB. Use this value to track the amount of space tempDB typically uses and plan for storage requirements. Each time SQL Server is restarted, tempDB is recreated using the default size. By default, tempDB grows automatically as needed. However, the files cannot be used during that process, and excessive autogrowth can lead to fragmentation. If tempDB typically needs to grow by a large amount, consider increasing the initial size. |
| TempDB Log File % Free Space |
The percentage of space allocated to the tempDB log file that is currently unused. Space in the tempDB log file is critical for transaction logging and rollback operations. Insufficient space can lead to transaction failures. |
| TempDB Log File Free Space |
The amount of space allocated to the tempDB log file that is currently unused. |
| TempDB Log File Size |
The amount of disk space currently allocated for the log file in the tempDB database. Each time SQL Server is restarted, tempDB is re-created, and the log file is created using the default size or the size specified by the DBA. If the tempDB log file requires more space, by default it autogrows as needed. However, autogrowth can affect performance because the tempDB log file cannot be used during autogrowth, and because autogrowth can lead to file fragmentation. Use the TempDB Log File Size metric to:
|
Metrics added for MS SQL Server and ASMI instances
| Metric | Description |
|---|---|
| TempDB % Free Space |
The percentage of unused space in tempDB. Space used in tempDB fluctuates based on the nature and volume of the SQL statements that are currently running. If tempDB fills up and cannot autogrow, the performance of all queries will be affected as they wait for access to tempDB. |
| TempDB Size |
The amount of space currently allocated for tempDB. Use this value to track the amount of space tempDB typically uses and plan for storage requirements. Each time SQL Server is restarted, tempDB is recreated using the default size. By default, tempDB grows automatically as needed. However, the files cannot be used during that process, and excessive autogrowth can lead to fragmentation. If tempDB typically needs to grow by a large amount, consider increasing the initial size. |
Licensing for Platform Connect CNS
In DPA 2025.4 and later, an instance must have a DBSH or DBSHDS license to send alert notifications to a third-party notification service through Platform Connect. If you are currently sending notifications from an instance that uses a subscription Category 1 or Category 2 license, contact your account representative for information about changing your license type.
CXCONSUMER advice improvement
The advice that DPA provides for reducing SQL Server CXCONSUMER waits has been updated and improved.
Fixed CVEs
At SolarWinds, we prioritize the swift resolution of CVEs to ensure the security and integrity of our software. In this release, we have successfully addressed the following CVEs.
Third-party CVEs
| CVE-ID | Vulnerability title | Description | Severity |
|---|---|---|---|
| CVE-2025-48989 | Apache Tomcat Improper Resource Shutdown or Release vulnerability | Improper Resource Shutdown or Release vulnerability in Apache Tomcat made Tomcat vulnerable to the made you reset attack. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.9, from 10.1.0-M1 through 10.1.43 and from 9.0.0.M1 through 9.0.107. Older, EOL versions may also be affected. Users are recommended to upgrade to one of versions 11.0.10, 10.1.44 or 9.0.108 which fix the issue. | 7.5 High |
| CVE-2025-55752 | Apache Tomcat Relative Path Traversal vulnerability | Relative Path Traversal vulnerability in Apache Tomcat. The fix for bug 60013 introduced a regression where the rewritten URL was normalized before it was decoded. This introduced the possibility that, for rewrite rules that rewrite query parameters to the URL, an attacker could manipulate the request URI to bypass security constraints including the protection for /WEB-INF/ and /META-INF/. If PUT requests were also enabled then malicious files could be uploaded leading to remote code execution. PUT requests are normally limited to trusted users and it is considered unlikely that PUT requests would be enabled in conjunction with a rewrite that manipulated the URI. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.10, from 10.1.0-M1 through 10.1.44, from 9.0.0.M11 through 9.0.108. The following versions were EOL at the time the CVE was created but are known to be affected: 8.5.6 through 8.5.100. Other, older, EOL versions may also be affected. Users are recommended to upgrade to version 11.0.11 or later, 10.1.45 or later or 9.0.109 or later, which fix the issue. | 7.5 High |
| CVE-2025-55754 | Apache Tomcat Improper Neutralization of Escape, Meta, or Control Sequences vulnerability | Improper Neutralization of Escape, Meta, or Control Sequences vulnerability in Apache Tomcat. Tomcat did not escape ANSI escape sequences in log messages. If Tomcat was running in a console on a Windows operating system, and the console supported ANSI escape sequences, it was possible for an attacker to use a specially crafted URL to inject ANSI escape sequences to manipulate the console and the clipboard and attempt to trick an administrator into running an attacker controlled command. While no attack vector was found, it may have been possible to mount this attack on other operating systems. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.10, from 10.1.0-M1 through 10.1.44, from 9.0.40 through 9.0.108. The following versions were EOL at the time the CVE was created but are known to be affected: 8.5.60 through 8.5.100. Other, older, EOL versions may also be affected. Users are recommended to upgrade to version 11.0.11 or later, 10.1.45 or later or 9.0.109 or later, which fix the issue. | 9.6 Critical |
| CVE-2025-61795 | Apache Tomcat Improper Resource Shutdown or Release vulnerability | Improper Resource Shutdown or Release vulnerability in Apache Tomcat. If an error occurred (including exceeding limits) during the processing of a multipart upload, temporary copies of the uploaded parts written to disc were not cleaned up immediately but left for the garbage collection process to delete. Depending on JVM settings, application memory usage and application load, it was possible that space for the temporary copies of uploaded parts would be filled faster than GC cleared it, leading to a DoS. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.11, from 10.1.0-M1 through 10.1.46, from 9.0.0.M1 through 9.0.109. The following versions were EOL at the time the CVE was created but are known to be affected: 8.5.0 through 8.5.100. Other, older, EOL versions may also be affected. Users are recommended to upgrade to version 11.0.12 or later, 10.1.47 or later or 9.0.110 or later which fixes the issue. | 5.3 Medium |
| CVE-2024-47072 | XStream Denial of Service (DoS) vulnerability | XStream is a simple library to serialize objects to XML and back again. This vulnerability may allow a remote attacker to terminate the application with a stack overflow error resulting in a denial of service only by manipulating the processed input stream when XStream is configured to use the BinaryStreamDriver. XStream 1.4.21 has been patched to detect the manipulation in the binary input stream causing the stack overflow and raises an InputManipulationException instead. Users are advised to upgrade. Users unable to upgrade may catch the StackOverflowError in the client code calling XStream if XStream is configured to use the BinaryStreamDriver. | 7.5 High |
| CVE-2025-48924 | Apache Commons Lang Uncontrolled Recursion vulnerability | Uncontrolled Recursion vulnerability in Apache Commons Lang. This issue affects Apache Commons Lang: Starting with commons-lang:commons-lang 2.0 to 2.6, and, from org.apache.commons:commons-lang3 3.0 before 3.18.0. The methods ClassUtils.getClass(...) can throw StackOverflowError on very long inputs. Because an Error is usually not handled by applications and libraries, a StackOverflowError could cause an application to stop. Users are recommended to upgrade to version 3.18.0, which fixes the issue. | 5.3 Medium |
Fixed customer issues
| Case number | Description |
|---|---|
| 01725725, 01731024, 01766632, 01778068, 01905740, 01922254, 01930166, 01988770, 02017698 | When any database in a monitored instance is not accessible, attempting to display index advisors no longer results in an error message. |
| 01988017 | Attempting to send DPA email notifications using the default mail server no longer fails with the following message:
|
| 01764650, 01991948 | In the Update DB Instance Connection Wizard, the users are no longer required to enter a value in the Port field when they enter a named instance and the port number is ignored. |
| 01975351 | Trends charts for MySQL database instances are displayed when database collation is set to Latin1_General_BIN. |
Installation or upgrade
For new installations, you can download the installer from the SolarWinds website or from the Customer Portal. For more information, see the DPA Installation and Upgrade Guide.
For upgrades, use the DPA Installation and Upgrade Guide to help you plan and execute your upgrade. When you are ready, download the upgrade package from the SolarWinds Customer Portal.
End of life
Integration with the SolarWinds Platform requires a supported version of the platform.
| Version | EoL announcement | EoE effective date | EoL effective date |
|---|---|---|---|
| 2023.4 | November 18, 2025: End-of-Life (EoL) announcement – Customers on DPA version 2023.4 or earlier should begin transitioning to the latest version of DPA. | February 18, 2026: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for DPA version 2023.4 or earlier will no longer actively be supported by SolarWinds. | February 18, 2027: End-of-Life (EoL) – SolarWinds will no longer provide technical support for DPA version 2023.4. |
See the End of Life Policy for information about SolarWinds product life cycle phases. To see EoL dates for earlier DPA versions, see DPA release history.
Deprecation notice
The following platforms and features are still supported in the current release. However, they will be unsupported in a future release. Plan on upgrading deprecated platforms, and avoid using deprecated features.
DPA server OS
Support for installing DPA on a server with a Windows Server 2012 R2 operating system is being removed.
Legal notices
© 2025 SolarWinds Worldwide, LLC. All rights reserved.
This document may not be reproduced by any means nor modified, decompiled, disassembled, published or distributed, in whole or in part, or translated to any electronic medium or other means without the prior written consent of SolarWinds. All right, title, and interest in and to the software, services, and documentation are and shall remain the exclusive property of SolarWinds, its affiliates, and/or its respective licensors.
SOLARWINDS DISCLAIMS ALL WARRANTIES, CONDITIONS, OR OTHER TERMS, EXPRESS OR IMPLIED, STATUTORY OR OTHERWISE, ON THE DOCUMENTATION, INCLUDING WITHOUT LIMITATION NONINFRINGEMENT, ACCURACY, COMPLETENESS, OR USEFULNESS OF ANY INFORMATION CONTAINED HEREIN. IN NO EVENT SHALL SOLARWINDS, ITS SUPPLIERS, NOR ITS LICENSORS BE LIABLE FOR ANY DAMAGES, WHETHER ARISING IN TORT, CONTRACT OR ANY OTHER LEGAL THEORY, EVEN IF SOLARWINDS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
The SolarWinds, SolarWinds & Design, Orion, and THWACK trademarks are the exclusive property of SolarWinds Worldwide, LLC or its affiliates, are registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other SolarWinds trademarks, service marks, and logos may be common law marks or are registered or pending registration. All other trademarks mentioned herein are used for identification purposes only and are trademarks of (and may be registered trademarks) of their respective companies.