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