Azure Player Blog

Blog Post

Last Week Reading (2021-11-28)

?? Press SynapseML: A simple, multilingual, and massively parallel machine learning library Microsoft just announced the release of SynapseML (previously known as MMLSpark) SSH File Transfer Protocol (SFTP) support...

2021-11-28

6 reads

Blog Post

Last Week Reading (2021-11-28)

? Press SynapseML: A simple, multilingual, and massively parallel machine learning library Microsoft just announced the release of SynapseML (previously known as MMLSpark) SSH File Transfer Protocol (SFTP) support...

2021-11-28

1 reads

Blog Post

SQL Server 2022 is coming

SQL Server 2022 is still in private preview (Microsoft MVP folks have access to it), but you can now read about the new release before it is released:  SQL...

2021-11-22

187 reads

Blogs

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...

The PASS Summit on Tour in Dallas

By

The PASS Summit goes on tour this year, with a September stop in Dallas....

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...

Formatting Dates and Times: The SQL Dialect Divide

By dbakevlar

Comments posted to this topic are about the item Formatting Dates and Times: The...

Query Plan Regressions --

By dbakevlar

Comments posted to this topic are about the item Query Plan Regressions --

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