Perhaps because they found that their poorly written code (IS NULL OR constructs) required it to perform acceptably?!? :hehe:

Still not sure about that being the issue though. Can you restore a backup of your database (probably pretty darn big given the table sizes you listed) and then set forced parameterization off and see if you get the same query plans?? Or maybe just change production for a few minutes off hours (if doable obviously)?