Brandie Tarvin wrote:
Thanks for the post about SQL 2022, Jeff. I've reached out to my team and mentioned that we need to fix all the problems we're currently having with SQL 2017 and 2019 ASAP before we push anyone on to 2022 just to make sure none of our code adds to the problem.
I wouldn't rush people, Brandie. Bad things happen when people rush. Like I say in one of my mantras, "If you want something real bad, that's the way you'll usually get it".
Eirikur and Ed (Wagner) have both confirmed the same issues in 2019 so nothing to do there. I've confirmed that there are no settings changes that make a difference compared to 2017. I'd install the 2017 stuff on a 2022 box and do some reasonable regression checking to see what is going to slow down and by how much before you start trying to fix the world of code on your side. While shooting a gun into the air is "fun", it's much more productive to have a target. 😀