Klaus Aschenbrenner

Klaus Aschenbrenner provides independent SQL Server Consulting Services across Europe and the US. Klaus works with the
.NET Framework and especially with the SQL Server 2005/2008 from the very beginnings. In the years 2004 - 2005 Klaus
was entitled with the MVP award from Microsoft for his tremendous support in the .NET Community. Klaus has also
written the book Pro SQL Server 2008 Service Broker which was published by Apress in the Summer of 2008. Further
information about Klaus you can find on his homepage at http://www.SQLpassion.at. He also twitters at
http://twitter.com/Aschenbrenner.

All authors

All authors

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