Back Yourself Up
Ever thought about yourself as a resource that should be backed up to minimize your loss?
2018-09-05
90 reads
Ever thought about yourself as a resource that should be backed up to minimize your loss?
2018-09-05
90 reads
What makes SQL Server professionals stick together? Can we draw any conclusions from this?
2017-07-10
127 reads
Are you a do-it-all DBA, or do you specialize in one aspect of database work?
2015-09-07
307 reads
Today we have a guest editorial from Hakim Ali. Being wrong is not as bad as you may think.
2012-07-11
442 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 SQL Server 2022 Clusterless Distributed...
Comments posted to this topic are about the item Navigating Multi Platform Realities in...
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