SQL Sentry 2026.3 release notes
Release date: September 1, 2026
Here's what's new in SQL Sentry 2026.3. You can find the applicable system requirements here.
To view release notes, system requirements, and product guide PDFs for supported versions of SQL Sentry, see SQL Sentry previous versions. To view release notes for multiple versions
New features and improvements in SQL Sentry
SSAS target support in SQL Sentry Portal
Watch your SSAS targets (MDX or Tabular) directly in SQL Sentry Portal. Review detailed SSAS metrics, and stay up to date with your SSAS target details on the Performance, SSAS Usage Totals, and Top Command tabs. See SQL Sentry Performance Analysis.
Export grid data in SQL Sentry Portal
Export detailed grid data directly from SQL Sentry Portal. See Getting Started in SQL Sentry Portal.
Microsoft Entra password support
SQL Sentry 2026.3 supports Microsoft Entra passwords for SQL Server and Azure SQL database targets.
General improvements
- Filter Deadlocks and waits collection in SQL Sentry.
Fixed customer issues
| Case number | Description |
|---|---|
| SQLS-755 | Running queries are collected for Azure SQL database targets in business critical and hyperscale tiers. |
| SQLS-723 | Top SQL completed queries for Azure SQL database targets populate the login username for SQL authentication users as expected. |
| SQLS-713 | Folders are visible to any user viewing an event chain. |
| SQLS-709 | Watching a SQL Sentry database target in an Availability Group does not consume a license. |
| SQLS-618 | Users can change credentials in Amazon RDS targets in SQL Sentry as expected when using authentication accounts other than Windows. |
| SQLS-412 | Procedure stats for stored procedures with the same name in different databases display the correct value for Text data with corresponding parameters. |
| Portal-1409 | The SQL Sentry Portal Always On tab populates as expected. |
End of life
| Version | EoL announcement | EoE effective date | EoL effective date |
|---|---|---|---|
| 2024.3.11 | September 1, 2026: End-of-Life (EoL) announcement – Customers on SQL Sentry version 2024.3.11 or earlier should begin transitioning to the latest version of SQL Sentry. | October 1, 2026: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for SQL Sentry version 2024.3.11 or earlier will no longer actively be supported by SolarWinds. | September 1, 2027: End-of-Life (EoL) – SolarWinds will no longer provide technical support for SQL Sentry version 2024.3.11. |
| 2024.3.9 | September 1, 2026: End-of-Life (EoL) announcement – Customers on SQL Sentry version 2024.3.9 or earlier should begin transitioning to the latest version of SQL Sentry. | October 1, 2026: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for SQL Sentry version 2024.3.9 or earlier will no longer actively be supported by SolarWinds. | September 1, 2027: End-of-Life (EoL) – SolarWinds will no longer provide technical support for SQL Sentry version 2024.3.9. |
| 2024.3 | September 1, 2026: End-of-Life (EoL) announcement – Customers on SQL Sentry version 2024.3 or earlier should begin transitioning to the latest version of SQL Sentry. | October 1, 2026: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for SQL Sentry version 2024.3 or earlier will no longer actively be supported by SolarWinds. | September 1, 2027: End-of-Life (EoL) – SolarWinds will no longer provide technical support for SQL Sentry version 2024.3. |
| 2024.2 | September 1, 2026: End-of-Life (EoL) announcement – Customers on SQL Sentry version 2024.2 or earlier should begin transitioning to the latest version of SQL Sentry. | October 1, 2026: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for SQL Sentry version 2024.2 or earlier will no longer actively be supported by SolarWinds. | September 1, 2027: End-of-Life (EoL) – SolarWinds will no longer provide technical support for SQL Sentry version 2024.2. |
| 2023.4 | November 18, 2025: End-of-Life (EoL) announcement – Customers on SQL Sentry version 2023.4 or earlier should begin transitioning to the latest version of SQL Sentry. | February 18, 2026: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for SQL Sentry 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 SQL Sentry version 2023.4. |
See the End of Life Policy for information about SolarWinds product life cycle phases. To see EoL dates for earlier SQL Sentry versions, see SQL Sentry release history.
Legal notices
© 2026 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.