<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Dynatrace Hub - Microsoft SQL Server latest releases</title><link>https://www.dynatrace.com/hub/detail/microsoft-sql-server-2/</link><description>A list of extensions from Microsoft SQL Server</description><atom:link href="https://hub-manager.hub.central.dynatrace.com/api/v1/public-hub/feed/extensions/microsoft-sql-server-2/" rel="self"/><language>en-us</language><lastBuildDate>Fri, 14 Aug 2026 18:50:27 +0000</lastBuildDate><item><title>Microsoft SQL Server 4.1.5</title><link>https://www.dynatrace.com/hub/detail/microsoft-sql-server-2/</link><description>&lt;ul&gt;
&lt;li&gt;Fixed a bug where smartscape on grail entities were not being generated correctly for named instances&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Fri, 14 Aug 2026 18:50:27 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/microsoft-sql-server-2/</guid></item><item><title>Microsoft SQL Server 4.1.3</title><link>https://www.dynatrace.com/hub/detail/microsoft-sql-server-2/</link><description>&lt;ul&gt;
&lt;li&gt;This extension is now using all rich visualization features of Grail within Infrastructure &amp;amp; Operations App.&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Thu, 30 Jul 2026 14:13:53 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/microsoft-sql-server-2/</guid></item><item><title>Microsoft SQL Server 4.0.0</title><link>https://www.dynatrace.com/hub/detail/microsoft-sql-server-2/</link><description>&lt;h2&gt;Breaking changes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Due to performance issues, dropped the unstable &lt;code&gt;db.connection_details&lt;/code&gt; and &lt;code&gt;id_classic&lt;/code&gt; attributes from Smartscape nodes. To prevent this issue in the future, version 3.1.2 and 3.1.3 have been unpublished. If upgrading from version 2.x.x to this version, see below the release notes for the changes in the unpublished versions:&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;3.1.3&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Managed&lt;/strong&gt;: Fixed a Unified Analysis screen definition that prevented data from being shown when execution interval for the extension was changed to any value higher than 1.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;3.1.2&lt;/h2&gt;
&lt;h3&gt;⚠️WARNING⚠️: Possible breaking changes and warnings - PLEASE READ before upgrading:&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;This version requires a &lt;em&gt;minimum Dynatrace version&lt;/em&gt; of &lt;code&gt;1.338.0&lt;/code&gt; and a &lt;em&gt;minimum EEC version&lt;/em&gt; of &lt;code&gt;1.337.0&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;This version includes a breaking change for Dynatrace on Grail.
&lt;ul&gt;
&lt;li&gt;With the inclusion of OpenPipeline processing rules, any metrics ingested from the extension will be processed by a dedicated OpenPipeline pipeline.&lt;/li&gt;
&lt;li&gt;This means that any dynamic route configured to process any metrics from the extension will be dropped in favor of the dedicated pipeline. Please, refer to &lt;a href="https://docs.dynatrace.com/docs/platform/openpipeline/concepts/pipeline-groups"&gt;pipeline groups&lt;/a&gt; to continue using dynamic routes.&lt;/li&gt;
&lt;li&gt;With the inclusion of OpenPipeline processing rules, any logs ingested from the extension will be processed by a dedicated OpenPipeline pipeline instead of the &lt;a href="https://docs.dynatrace.com/docs/shortlink/lma-classic-log-processing"&gt;classic log pipeline&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;This means that classic rules will no longer be used on logs ingested from the extension. Please be sure to migrate any you still need to &lt;a href="https://docs.dynatrace.com/docs/shortlink/lma-openpipeline"&gt;OpenPipeline rules&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Additionally, some field names are &lt;a href="https://docs.dynatrace.com/docs/platform/openpipeline/concepts/processing#pipeline"&gt;handled differently&lt;/a&gt; in OpenPipeline, e.g. capitalization. Please double-check any custom dashboards and alerts you have created for this extension.&lt;/li&gt;
&lt;li&gt;You must opt-in to OpenPipeline configuration via Settings API – see the &lt;a href="https://docs.dynatrace.com/docs/shortlink/openpipeline-migration-settings"&gt;documentation&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Feature sets have been refactored, with new feature sets added and some other ones removed, meaning that in most cases, you will need to re-create monitoring configurations when updating to this version, as well as check properly all the new feature sets to ensure you're enabling the same insights as before.&lt;/li&gt;
&lt;li&gt;SQL Agent removed from Classic Topology.&lt;/li&gt;
&lt;li&gt;Log entries captured from the &lt;code&gt;agent_requests&lt;/code&gt; and &lt;code&gt;application_requests&lt;/code&gt; event groups have been removed in favor of the generic &lt;code&gt;all_requests&lt;/code&gt; event group. Please use the &lt;code&gt;program_name&lt;/code&gt; attribute to correctly filter for agent or application requests.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;New in this version:&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://docs.dynatrace.com/docs/platform/grail/smartscape-on-grail"&gt;Smartscape on Grail&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Added feature set metadata for recommended metrics.&lt;/li&gt;
&lt;li&gt;Fixed a bug where the &lt;code&gt;failed_jobs&lt;/code&gt; query was returning the server name in a different format than the rest of the queries, generating duplicate entities.&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Wed, 22 Jul 2026 09:36:27 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/microsoft-sql-server-2/</guid></item><item><title>Microsoft SQL Server 2.11.8</title><link>https://www.dynatrace.com/hub/detail/microsoft-sql-server-2/</link><description>&lt;ul&gt;
&lt;li&gt;(Platform) Fixed filtering for &lt;code&gt;dt.entity.sql:sql_server_database&lt;/code&gt; charts in Infrastructure &amp;amp; Operations app.&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Mon, 04 May 2026 15:18:19 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/microsoft-sql-server-2/</guid></item><item><title>Microsoft SQL Server 2.11.7</title><link>https://www.dynatrace.com/hub/detail/microsoft-sql-server-2/</link><description>&lt;ul&gt;
&lt;li&gt;Refactored failed jobs query to make it more efficient.&lt;/li&gt;
&lt;li&gt;(Managed) Fixed metric events to be attached to the right entity.&lt;/li&gt;
&lt;li&gt;(Platform) Fixed alerting templates so they are attached to the right entity.&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Thu, 23 Apr 2026 08:34:16 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/microsoft-sql-server-2/</guid></item><item><title>Microsoft SQL Server 2.11.5</title><link>https://www.dynatrace.com/hub/detail/microsoft-sql-server-2/</link><description>&lt;p&gt;Fixes and Improvements:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Entity &lt;code&gt;sql:sql_server_instance&lt;/code&gt; would display a duplicate for a short period of time after ingesting logs. Topology rules have been corrected.&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Mon, 23 Feb 2026 13:30:34 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/microsoft-sql-server-2/</guid></item><item><title>Microsoft SQL Server 2.11.1</title><link>https://www.dynatrace.com/hub/detail/microsoft-sql-server-2/</link><description>&lt;h3&gt;New Features&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Added ALERT_TEMPLATES for anomaly detectors in the Davis Anomaly Detection app.&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Wed, 10 Dec 2025 10:01:05 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/microsoft-sql-server-2/</guid></item><item><title>Microsoft SQL Server 2.11.0</title><link>https://www.dynatrace.com/hub/detail/microsoft-sql-server-2/</link><description>&lt;h3&gt;New Features&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Added Worker Metrics to the Default Feature Set&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Active Workers&lt;/strong&gt;: Displays the number of workers actively executing tasks.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Max Workers&lt;/strong&gt;: Shows the maximum number of workers that can be active.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Worker Threads Percentage&lt;/strong&gt;: Indicates the percentage of worker threads currently in use.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Added Query Performance Metric to the Queries Feature Set&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Percent of Elapsed Time for Requests Wait Type&lt;/strong&gt;: Represents the percentage of elapsed time for requests categorized by wait type performance counter.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Added @@servername as a New Attribute&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Added as an additional attribute to Server Instances.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;hr /&gt;
&lt;h3&gt;Improvements&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Updated {device.name} to {device} on database instances, enabling the database name to appear in the naming string.&lt;/li&gt;
&lt;/ul&gt;
&lt;hr /&gt;
&lt;h3&gt;Bug Fixes&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Failed Distributed Transactions Query Updated&lt;/strong&gt;
&lt;ul&gt;
&lt;li&gt;Resolved an issue where a temporary duplicate could occur if an orphaned query was recorded.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;hr /&gt;
&lt;h3&gt;Future Breaking Change&lt;/h3&gt;
&lt;p&gt;In a future update &lt;code&gt;Transaction Logs&lt;/code&gt; and &lt;code&gt;Transaction logs&lt;/code&gt; FeatureSets will be merged into one.&lt;/p&gt;
</description><pubDate>Thu, 04 Dec 2025 21:01:53 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/microsoft-sql-server-2/</guid></item><item><title>Microsoft SQL Server 2.10.4</title><link>https://www.dynatrace.com/hub/detail/microsoft-sql-server-2/</link><description>&lt;h5&gt;Potential Breaking Change affecting &lt;strong&gt;Availability Replica Entities&lt;/strong&gt;&lt;/h5&gt;
&lt;h2&gt;Bug Fix:&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Availability Replica would not handle name instances correctly. This has been fixed and now relationship mapping will happen as expected. The previously incorrect entities may no longer appear.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;Dimension Changes:&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;Product Version&lt;/code&gt; Dimension has now been changed to &lt;code&gt;DB Instance Version&lt;/code&gt; on SQL Server Instance Entity. This is now a standardized value across Database Extensions.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;Attribute Changes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;All Entities created by the SQL Server Extension now have the &lt;code&gt;security_context&lt;/code&gt; attribute which is entered via the Monitoring Configuration.&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Thu, 11 Sep 2025 07:05:28 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/microsoft-sql-server-2/</guid></item><item><title>Microsoft SQL Server 2.10.1</title><link>https://www.dynatrace.com/hub/detail/microsoft-sql-server-2/</link><description>&lt;h2&gt;Bugfix&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;failed_jobs&lt;/code&gt; previously would ingest job failures older than 5 minutes depending on the time of hour. This has been corrected.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;Warning&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;Transaction Logs&lt;/code&gt; featureSet to be removed in a future update. &lt;code&gt;Transaction logs&lt;/code&gt; will continue to exist&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Fri, 04 Jul 2025 08:22:39 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/microsoft-sql-server-2/</guid></item><item><title>Microsoft SQL Server 2.10.0</title><link>https://www.dynatrace.com/hub/detail/microsoft-sql-server-2/</link><description>&lt;h1&gt;Improvements&lt;/h1&gt;
&lt;ul&gt;
&lt;li&gt;Added new alert &lt;code&gt;SQL Server is unreachable&lt;/code&gt; to monitor database availability, based on &lt;code&gt;Uptime metric&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Uptime visualization updated from single value display to graph chart visualization for better alert investigation&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Tue, 01 Jul 2025 08:46:28 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/microsoft-sql-server-2/</guid></item><item><title>Microsoft SQL Server 2.9.3</title><link>https://www.dynatrace.com/hub/detail/microsoft-sql-server-2/</link><description>&lt;p&gt;&lt;strong&gt;Bug fixes&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Current Jobs query syntax fix. This was causing a breakage of the extension&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Warning&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&amp;quot;Transaction Logs&amp;quot; featureSet to be removed in a future update. &amp;quot;Transaction logs&amp;quot; will continue to exist.&lt;/li&gt;
&lt;li&gt;Minimum EEC version increased (1.303) for Query Interval which was causing breakage issues when updating to 2.7.0 and above&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Fri, 06 Jun 2025 07:53:03 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/microsoft-sql-server-2/</guid></item><item><title>Microsoft SQL Server 2.9.2</title><link>https://www.dynatrace.com/hub/detail/microsoft-sql-server-2/</link><description>&lt;p&gt;&lt;strong&gt;Bug fixes&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;buffer_cache_hit bundled alert now fixed.&lt;/li&gt;
&lt;li&gt;Minimum EEC version increased to 1.303 for Query Interval which was causing breakage issues when updating to 2.7.0 and above&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Improvements&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;event.group added for agent and application queries log ingest&lt;/li&gt;
&lt;li&gt;Added &amp;quot;Job Category id&amp;quot; and &amp;quot;Job Category name&amp;quot; to Current and Failed Jobs&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Features&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Now able to see the &lt;code&gt;locks and waits&lt;/code&gt; of impacted requests.&lt;/li&gt;
&lt;li&gt;Added Gen 3 dashboard to visualize the &lt;code&gt;locks and waits&lt;/code&gt; data&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Warning&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&amp;quot;Transaction Logs&amp;quot; featureSet to be removed in a future update. &amp;quot;Transaction logs&amp;quot; will continue to exist.&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Tue, 27 May 2025 12:55:28 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/microsoft-sql-server-2/</guid></item><item><title>Microsoft SQL Server 2.8.0</title><link>https://www.dynatrace.com/hub/detail/microsoft-sql-server-2/</link><description>&lt;p&gt;&lt;strong&gt;New Feature&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Configurable frequency for the SQL queries&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Thu, 01 May 2025 13:16:13 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/microsoft-sql-server-2/</guid></item><item><title>Microsoft SQL Server 2.7.5</title><link>https://www.dynatrace.com/hub/detail/microsoft-sql-server-2/</link><description>&lt;p&gt;Adds the SAME_AS relationship between SQL Instances and related Process Group Instances on OneAgent monitored hosts.&lt;/p&gt;
</description><pubDate>Fri, 25 Apr 2025 18:07:18 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/microsoft-sql-server-2/</guid></item><item><title>Microsoft SQL Server 2.7.3</title><link>https://www.dynatrace.com/hub/detail/microsoft-sql-server-2/</link><description>&lt;p&gt;&lt;strong&gt;Features:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Added a built-in dashboard for 3rd gen SaaS tenants.&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Fri, 04 Apr 2025 22:08:22 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/microsoft-sql-server-2/</guid></item><item><title>Microsoft SQL Server 2.7.1</title><link>https://www.dynatrace.com/hub/detail/microsoft-sql-server-2/</link><description>&lt;h4&gt;Fixed in this version:&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;Sorting SQL statements in Databases app would produce duplicate results&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Mon, 06 Jan 2025 11:48:02 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/microsoft-sql-server-2/</guid></item><item><title>Microsoft SQL Server 2.7.0</title><link>https://www.dynatrace.com/hub/detail/microsoft-sql-server-2/</link><description>&lt;h5&gt;New Entity&lt;/h5&gt;
&lt;ul&gt;
&lt;li&gt;SQL Agent added to topology&lt;/li&gt;
&lt;/ul&gt;
&lt;h5&gt;New Metrics&lt;/h5&gt;
&lt;ul&gt;
&lt;li&gt;Agent Status&lt;/li&gt;
&lt;li&gt;Failed Distributed Transactions Count&lt;/li&gt;
&lt;/ul&gt;
&lt;h5&gt;New Log Ingests&lt;/h5&gt;
&lt;ul&gt;
&lt;li&gt;Top 25 Agent Queries running longer than 60 seconds&lt;/li&gt;
&lt;li&gt;Top 25 Application Queries running longer than 60 seconds&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;Bug Fixes&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Fixed an issue where Databases App did not display Uptime Hours due to syntax error.&lt;/li&gt;
&lt;li&gt;Fixed Arithmetic Overflow Error that had a chance to occur in large environments on the Largest Files Managed calculation.&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Wed, 27 Nov 2024 10:33:42 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/microsoft-sql-server-2/</guid></item><item><title>Microsoft SQL Server 2.6.0</title><link>https://www.dynatrace.com/hub/detail/microsoft-sql-server-2/</link><description>&lt;h2&gt;Improvements&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Execution Plan fetching now done in Databases App&lt;/li&gt;
&lt;li&gt;Instance entity parsing from log records&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;Changes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Removed query plan from longest_queries query&lt;/li&gt;
&lt;li&gt;Show latest back-up age&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Thu, 17 Oct 2024 04:22:37 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/microsoft-sql-server-2/</guid></item><item><title>Microsoft SQL Server 2.5.4</title><link>https://www.dynatrace.com/hub/detail/microsoft-sql-server-2/</link><description>&lt;p&gt;&lt;strong&gt;Improvements&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Added default value for &lt;code&gt;availability.replica.instance&lt;/code&gt; dimension: &lt;code&gt;MSSQLSERVER&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;This enables the SAME AS relationship between the &lt;code&gt;sql:sql_server_instance&lt;/code&gt; and &lt;code&gt;sql:sql_server_availability_replica&lt;/code&gt; entities based on the equality of their respective attributes: &lt;code&gt;server = ar_server_name&lt;/code&gt; and &lt;code&gt;instance = ar_instance_name&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;Previously, if the replica was running on an instance that had a default name, the relationshp wasn't being established.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Fri, 09 Aug 2024 18:27:11 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/microsoft-sql-server-2/</guid></item></channel></rss>