Optimized Plan Forcing with Query Store in SQL Server 2022

Question

Optimized Plan Forcing with Query Store in SQL Server 2022

Almighty

SSCrazy

Points: 2001
More actions
September 4, 2023 at 12:00 am

#4252115

Comments posted to this topic are about the item Optimized Plan Forcing with Query Store in SQL Server 2022

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply

Jeff Moden SSC Guru Points: 1004378 More actions · Answer 1

My problem with Query Store and some of the people that use it is that, quite frequently, many of the plans (there's just 2 or there's more) are terrible. A lot of people think they're doing a good thing when, in reality, they forcing the best of two plans that are both terrible. Very few actually say, "This is a temporary patch... I'm opening a ticket to get it rewritten". 😉

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

jheim Right there with Babe Points: 714 More actions · Answer 2

Thanks Prakash,

Though plan guides and pinning plans has been available in earlier versions, this exemplifies how much easier it is with querystore features in 2022. Thanks

MMartin1 One Orange Chip Points: 27795 More actions · Answer 3

Good article thank you. An important item to note > Microsoft Docs itselft mentions that forced plans are a temporary solution as a optimized plan today may not be the best plan tomorrow

----------------------------------------------------