The Bizarre Problems With SQL Server Query Optimizers

The optimizer doesn't do a very good job of knowing when to kind of recompile and run the query differently. One trick is to always set your local variables that just copy the arguments that you pass in. And it kind of forces the optimizer to kind of read you the work, I guess. It's bizarre because we're talking about an historic procedure in a store product. But for some reason, the parameter sniffing, I don't know why, but it just doesn't seem to, to, to hit it all the time.