When dealing with wonky nonsense in plans, Instead of WHERE 1 = (SELECT 1), I smack the monitor and then blow in the USB port.
@ErikDarlingDataАй бұрын
Throw the controller against the wall
@mortezasafaee6981Ай бұрын
Keep going... i like you haircut😊
@ErikDarlingDataАй бұрын
Thank you 😁
@worldfromtheairАй бұрын
Slightly off topic, but I guess you also use DATA_COMPRESSION = PAGE on all your index creates too? I guess just to save space and logical reads
@ErikDarlingDataАй бұрын
Just space. I don't care about logical reads: kzbin.info/www/bejne/oanadp6bd6iVmqc
@IcarianHeightsАй бұрын
Apologies for being dense, but even after watching the video and reading the blog post, though I better understand why you're using `1 = (SELECT 1)`, I still don't understand why that pattern forces the optimizer to skip assigning the query as having a `trivial plan` or `simple parameterization`. Is it simply because it's a sub-query, where the optimizer doesn't know what may be in it at runtime so it has to in fact go down the actual road of optimizing the query further than if it were a known/constant value?
@ErikDarlingDataАй бұрын
Yep, you can even simplify it in some cases to be something like SELECT (SELECT Id) FROM dbo.Whatever;
@andreysamykin1143Ай бұрын
Thanks for an interesting video! I wonder if “when 1=1” has the same effect.