SQL Sentry 2026.1 release notes
Release date: February 24, 2026
Here's what's new in SQL Sentry 2026.1. 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
Add user logins in SQL Sentry Portal
Set user logins directly in SQL Sentry Portal. SQL Sentry Portal Administrator accounts can add logins to Portal users through the User Management page. See Portal Security.
SMTP Microsoft Exchange Online Support
SQL Sentry 2026.1 supports OAuth 2.0 for SMTP servers. Switch between basic authentication, or Microsoft Exchange online on the SMTP server editor.
See SMTP Settings.
SQL Server 2025 Support
SQL Sentry 2026.1 supports monitoring SQL Server 2025 targets and SQL Server 2025 as the repository database.
Contained Availability Groups - Tech Preview
View collected job details on the Calendar for contained availability groups. Because this feature is in tech preview, you will need to enable it through the feature flag. See AlwaysOn Availability.
Fixed customer issues
| Case number | Description |
|---|---|
| 1418365 | Improved counter collection support in NTLM disabled environments. |
| 1397157 | Event chain connectivity checks logging and process improvements. |
| 1331284 | Event chains added to the Even Chain folder in the Navigator appear as expected. |
Installation or upgrade
End of life
| Version | EoL announcement | EoE effective date | EoL effective date |
|---|---|---|---|
| 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.
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.
Alert URLS
Alert URLS that redirect to the SQL Sentry Client will be removed in version 2026.2.
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.