Performance Tuning Using Extended Events: Part 2
Part 2 of identifying performance puning opportunities using Extended Events. Learn how about shredding XML.
2019-12-23
8,087 reads
Part 2 of identifying performance puning opportunities using Extended Events. Learn how about shredding XML.
2019-12-23
8,087 reads
Identifying Performance Tuning Opportunities Using Extended Events: Part 3 Aggregate Report
2019-12-20 (first published: 2017-05-04)
6,002 reads
In this article, learn how to identify performance tuning opportunities using Extended Events.
2019-12-06 (first published: 2017-04-20)
17,818 reads
This article by Brian Davey describes how to setup log shipping for a large number of databases minimizing the number of jobs needed thus significantly reducing CPU and memory usage.
2011-09-28
11,510 reads
In this article Brian Davey present a solution for changing the text in multiple stored procedures using T-SQL.
2011-03-28
11,344 reads
I am responding late to a T-SQL Tuesday invite from John Sterrett. John’s call...
It’s been forgotten about and neglected for few years but I’ve decided to dust...
I am honored to announce that I have been renewed as a Microsoft MVP...
Comments posted to this topic are about the item How a Legacy Logic Choked...
Comments posted to this topic are about the item People Make Odd Choices
Comments posted to this topic are about the item SQL Server 2022 Clusterless Distributed...
For the Question of the day, I am going to go deep, but try to be more clear, as I feel like I didn't give enough info last time, leading folks to guess the wrong answer... :) For today's question: You’re troubleshooting a performance issue on a critical stored procedure. You notice that a previously efficient query now performs a full table scan instead of an index seek. Upon investigating, you find that an NVARCHAR parameter is being compared to a VARCHAR column in the WHERE clause. What is the most likely cause of the query plan regression?
See possible answers