Test Day 2: SSMS 22.5 Copilot & Extended Events (Stop Digging into .XEL Files!)

Before we dive in, catch up on the previous episodes of my SSMS 22.5 deep-dive:
🔗 SQL Server: SSMS 22.5.0 Changes How You Work
🔗 Test Day 1: SSMS 22.5 Copilot vs. Complex Execution Plans

In this post, I’ll show you how the brand-new GitHub Copilot integration in SSMS 22.5.0 instantly translates thousands of cryptic Extended Events XML rows into clear, actionable performance insights. Stop wasting hours parsing .xel files and let AI pinpoint your database deadlocks in seconds!

TL;DR: What's New with XEvents & AI

  • ✔️ Semantic Log Analysis: Copilot now summarizes .xel files, identifying recurring error patterns instantly. 🔍
  • ✔️ "Natural Language" XEvents: Create new monitoring sessions simply by describing what you want to track. ✍️
  • ✔️ Deadlock Visualizer 2.0: The AI graphically explains blocking chains and suggests optimal isolation levels. ⛓️
  • ✔️ UI Stability: Improved rendering of the XEvent dashboard across multi-monitor setups. 🖥️

Hi SQL Server Guys,

We all know how important it is to make every second count when managing SQL Server environments. SSMS 22.5.0 brings key updates that will revolutionize the way we troubleshoot databases. After the massive success of yesterday's field test on execution plans, I wanted to raise the bar today.

Let's be honest: Extended Events are an incredibly powerful tool, but analyzing the collected data is often a complete nightmare of complex filters and manual XML parsing. With the April 2026 release of SSMS 22.5.0, Microsoft dropped a "hidden" but brutal feature: Copilot for XEvents Analysis. Let’s see how it handled a simulated CPU spike and deadlock storm in my lab.

What It Really Is

GitHub Copilot in SSMS has expanded its context window directly into the results pane and the Extended Events viewer. According to the official Microsoft documentation, the AI is now schema-aware and can interpret live output. Instead of manually exporting a deadlock graph and hunting for the victim, Copilot reads the XEvent payload natively and cross-references it with your database objects to give you a natural language breakdown.

🧪 The Field Test: From Chaos to Solution in 30 Seconds

I simulated a classic production problem: a legacy application generating hundreds of small deadlocks every hour, heavily disguised because they originated from different compiled stored procedures.

Instead of digging through the XML row by row, I opened the XEvent Live Data viewer in SSMS 22.5.0 and simply asked Copilot:

"Analyze the last 10 deadlock events. What is the most contested object, and which query is constantly losing the resource competition?"

💣 The AI's Answer

Copilot didn't just point out that the Sales.Invoices table was the bottleneck. It explicitly highlighted that the conflict occurred between a massive batch UPDATE and a reporting SELECT that was lacking proper locking hints. 

-- 🤖 Copilot's suggestion to immediately mitigate the deadlock
-- After analyzing the XEvent session, Copilot suggests:
ALTER DATABASE [SalesDB] SET READ_COMMITTED_SNAPSHOT ON;

-- Alternatively, for the specific query:
SELECT * FROM Sales.Invoices WITH (NOLOCK) WHERE InvoiceDate = GETDATE();

🚀 My REAL Strategy

The integration of Copilot with Extended Events completely changes the rules of the game for 3 AM troubleshooting. Translating a binary log file into a conversational diagnostic report is priceless.

However, here is my advice as an "old wolf" of the DB world: do not let the AI dictate your isolation strategy.

Copilot will frequently suggest NOLOCK or Snapshot Isolation as a "magic wand" to fix blocking, but it is up to us to evaluate the impact on data consistency (like dirty reads). Use the AI to find the needle in the haystack, but rely on your expertise to sew the solution.

Pro-tip: Analyzing logs via Copilot consumes context tokens. If you are dealing with gigabytes of .xel files, make sure to natively filter the time range in SSMS before invoking the assistant to avoid hitting context limits.

Related Posts

📢 Support the Blog: Did you find this deep-dive helpful? The ads you see here are selected to reflect your interests. If a partner's offer catches your eye, give it a look! Your engagement helps me continue publishing premium SQL Server content for the community.

Biondi Luca @2026 - Sharing over 25 years of Gained Knowledge for Passion. Share if you like my posts!

Comments

Post a Comment

I Post più popolari

Speaking to Sql Server, sniffing the TDS protocol

Image
Hello friends!  If yesterday you read my post and found it definitely boring (for the topic of course and not for how it was written to the author 😁) well today I promise you that the topic will be much more interesting! Let's talk about Sniffing , let's talk about going to see what happens when we "log in" or when we send a Query to SQL Server.  We will do this by taking a look to the little known tabular data stream (TDS) protocol built on top of the TCP/IP protocol. Ready! The TDS protocol What is the Tabular data stream (TDS) protocol?  The TDS is the protocol used by the SQL Server client Net-Library to communicates with SQL Server . TDS is specific to SQL Server and it is a low-level protocol that specifies both commands and data in a specific arrangement.  TDS encapsulate the TCP/IP protocol. Sniffing TDS packets you can read from the network the requests that your application do to the SQL Server and read the answer .   How to Sniff data from the ne...
Read more

SQL Server, find text in a Trigger, Stored Procedures, View and Function. Two ways and what ways is better

Image
Hi guys, Welcome back! Today a light post about a question that has been asked to me several times. The question is: how to  search for text inside a trigger or a stored procedure ? We have two different ways. A first way using a system view called syscomments: SELECT obj.xtype, text , * FROM sysobjects obj JOIN syscomments com on obj.id = com.id WHERE TEXT like '%text_that_i_am_searching_for%' A second way using a system view called sql_module: SELECT o. name AS Object_Name, o. type_desc , m. definition FROM sys.sql_modules m JOIN sys.objects o ON m. object_id = o. object_id WHERE m. definition Like '%text_that_i_am_searching_for%' ;   Another question is? What differences do we have in using one way instead of the other? Which solution is better? You have to consider that the system view sys.syscomment is obsolete and will be removed sooner or later. So don't use it in production enviroiments. The sys.sql_m...
Read more

SQL Server, Avoid that damn Table Spool!

Image
Hi guys, Welcome back for another post! A light one inspired from what i do during my work: many times I optimize queries rewriting them or adding index and i like it very much! Sometimes you need to use a little imagination, but everything you learn ... sooner or later it will come in handy! Enjoy the reading mates! Avoid the Table Spool, when you can A few days ago I came across a query whose execution time was very high ... or so it was for the client complaining about the problem. Before recreating it, let's create the structures and fill the tables with some data Create table PriceList (Id int identity (1,1) primary Key ,Code Varchar (20)) Insert into PriceList (code) select top 1000 right( '0000' + cast ( row_number () over ( order by id) as varchar (4)),4) from artico Insert into PriceList (code) select top 4000 right( '1000' + cast ( row_number () over ( order by id) as varchar (4)),4) from artico Create table OrdersList (Id int identity...
Read more