October 6, 2014 at 5:56 pm
We bumped down the memory to 128 Gb on the SQL2, and we see the same plan as SQL1. Kind of throws all logic out of the window. But Paul White's article explains it.
Thanks everyone for sharing your insights!
October 6, 2014 at 5:57 pm
we are able to match up the execution plan by throttling the max memory setting in Server 1.
Here's the KB http://support.microsoft.com/kb/2413549 that explains more memory could sometimes cause inefficient plans! Thank you Microsoft!
Thanks to Paul White for pointing this out in a different thread for a different issue.
Thank you everyone for taking time and looking into this.
However, still curious of what "occasionally" means in the KB article's CAUSE section!
Thanks
Jagan K
Viewing 2 posts - 16 through 17 (of 17 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy