John

John Morehouse is currently a Consultant with Denny Cherry & Associates living in Louisville, Kentucky. With over 2 decades of technical experience in various industries, John now focuses on the Microsoft Data platform and specializes in Microsoft SQL Server. He is honored to be a Microsoft Data Platform MVP, 2016 Idera Ace, Friend of Red Gate since 2015, Sentry One PAC member & Community Ambassador. John has passion around speaking, teaching technical topics and giving back to the technical community. He is a user group leader, SQL Saturday organizer, and former PASS regional mentor. He is also a blogger, avid tweeter, and a frequent speaker at SQL Saturday's as well as other conferences. If you want to find John, you can find him on Twitter (@sqlrus) or on his blog, http://sqlrus.com.

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