I'm working on the SQL Server performance area and I want to know that is the Parameter Sniffing problem resolved in SQL Server 2022 completely ?

What trace flags are useful in this area ?

Thanks in advance.


1 Answer 1


No it is not.

See this article Brent Ozar wrote about it.


Small problem: we still have sniffing. Try running it for, say, Reputation = 3 and review the actual query plan ... then free the cache and see the difference.

Medium problem: direct equality searches only. The PSPO implementation is more of a down payment than a full payment. It only works for equality searches, not range searches. One of the most common parameter sniffing problems is the date range issue: queries with start & end date parameters, like this.

Large problem: monitoring software is doomed. If you look closely at the sp_BlitzCache screenshots, there’s a huge, massive, giant, unbelievably big new problem.... SQL Server can no longer tell where the query came from. It’s like every running statement is suddenly dynamic SQL with no parent... If you think that’s bad, there’s no way to join to the underlying statements. That’s not just bad, it’s poor. Really, really poor.


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.