SQL Server Blocking Monitoring
Monitoring blocking can be problematic when you cannot catch it in the act. This article will show you an easy way to configure a SQL Server Profiler Trace to monitor blocking
2011-05-19
12,184 reads
BJ Hermsen
Recovering data from corrupt tables using non-clustered indexes
At times database corruption happens and no good recovery path is available. It is possible to salvage data from indexes using query hints.
2010-01-19
5,975 reads
Blogs
TSQL Tuesday #188 Growing community
I am responding late to a T-SQL Tuesday invite from John Sterrett. John’s call...
Time to Revive our YouTube Channel
It’s been forgotten about and neglected for few years but I’ve decided to dust...
Microsoft MVP 2025: Continuing the Data Platform Journey
I am honored to announce that I have been renewed as a Microsoft MVP...
Forums
How a Legacy Logic Choked SQL Server in a 30-Year-Old Factory
Comments posted to this topic are about the item How a Legacy Logic Choked...
People Make Odd Choices
Comments posted to this topic are about the item People Make Odd Choices
SQL Server 2022 Clusterless Distributed Availability Group
Comments posted to this topic are about the item SQL Server 2022 Clusterless Distributed...
Question of the Day
Query Plan Regressions --
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