Damian is Microsoft MVP and Certified Trainer with 20 years of experience. Now trying to share the passion and knowledge among others. He runs the blog with his daughter as she is really passionate about technology

Tea and Iphone placed on table with leaves

Weekly reading #14

SQLDay starts in a week! Stay tuned during this week as it could be full of surprises! We are ready & prepared and speakers start to arrive next Saturday!...

2019-05-05

13 reads

Person holding a cup

Weekly reading #11

Good day folks! Let’s make this week great (again)! It is spring already there so it is easy to get up at 6am and write the blog! Now looking...

2019-04-15

50 reads

Blogs

Time to Revive our YouTube Channel

By

It’s been forgotten about and neglected for few years but I’ve decided to dust...

Microsoft MVP 2025: Continuing the Data Platform Journey

By

I am honored to announce that I have been renewed as a Microsoft MVP...

What is KTLO? Keep The Lights On vs Project Work in Agile

By

🔍 Demystifying KTLO: A Deep Dive into Keep The Lights On Work in IT...

Read the latest Blogs

Forums

How a Legacy Logic Choked SQL Server in a 30-Year-Old Factory

By Chandan Shukla

Comments posted to this topic are about the item How a Legacy Logic Choked...

Navigating Multi Platform Realities in My Database Life

By dbakevlar

Comments posted to this topic are about the item Navigating Multi Platform Realities in...

Import/Export SSMS Settings issue

By Brandie Tarvin

I have tried a number of times to export and then import my SSMS...

Visit the forum

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