Features and Fixes in SentryOne 19.2

Aaron Bertrand

Published On: October 16, 2019

Categories: SQL Sentry, SentryOne, DB Sentry 0

We are excited to announce the release of SentryOne 19.2, which includes completed queries for DB Sentry, as well as some additional enhancements and fixes. Let’s take a look at each of the new features.

58250—Top SQL Completed Queries for Azure SQL Database

This feature is easily the most important update in this release. The screenshot below shows completed queries and query history in Top SQL for an Azure SQL Database target. You will notice that Top SQL in DB Sentry is now remarkably similar to what you would see in SQL Sentry for an on-premises SQL Server target.

 

Azure SQL Database Completed Queries

 

Note that if you are upgrading from an earlier version of DB Sentry, you will need to ensure that Collect Trace Events and Collect Statement Events are enabled after the upgrade, and that the target allows creating SentryOne objects. Because of the way we’ve changed our collection techniques from the simple DMV polling in earlier versions, these settings are disabled during an upgrade, and you will need to “opt in” to the new behavior.

Check out this video for a walk through of DB Sentry’s Azure SQL Database Top SQL.

Top SQL parity is the first in a string of DB Sentry enhancements planned for the coming months. Other enhancements include Azure Active Directory (AAD) authentication, elastic pool support, blocking, deadlocks, and index and statistics management. We’ll have more to share about these changes soon.

53140—Top SQL Memory Allocation Columns

We have added a handful of optional columns to Top SQL in SQL Sentry. These columns provide more information about memory usage for a given statement. The following screenshot shows a few of these columns on the Completed Queries grid and the rest of the columns that are now available in the column chooser.

 

Top SQL Memory Allocation Columns

 

52419—Columnstore and In-Memory OLTP Memory Counters

The SQL Sentry Performance Analysis Dashboard now shows memory-optimized and columnstore memory usage on the SQL Server Memory chart. In the following screenshot, you can see a sliver of columnstore memory usage on the chart.

 

Columnstore and In-Memory OLTP Memory Counters

 

Fixes in SentryOne 19.2

  • 50094—Addressed an issue where alerts involving the blocking SQL duration were not functioning properly when combined with a ruleset
  • 52164—Updated the VMware Disk I/O charts so that the units are now expressed in MB instead of KB
  • 55441—Worked around a behavior that involved SQL Sentry trying to capture disk metrics from an offline database

 

Get Started with SentryOne 19.2 Today!

Interested in trying out the new features in SentryOne 19.2? Follow these instructions to upgrade to the latest version or download a free trial today!

View a full list of the features and fixes included in SentryOne 19.2 here.

Aaron (@AaronBertrand) is a Product Manager at SentryOne, with industry experience dating back to Classic ASP and SQL Server 6.5. He is editor-in-chief of the performance-related blog, SQLPerformance.com, and serves as a community moderator for the Database Administrators Stack Exchange. Aaron's blog focuses on T-SQL bad habits and best practices, as well as coverage of updates and new features in Plan Explorer, SentryOne, and SQL Server.


Comments