Maximum server memory change taking a long time, don’t panic

So, you’ve changed the Maximum server memory option and the server property box appears to have hung, what do you do?
The short answer: wait.

You can view the current errorlog e.g. xp_readerrorlog, and once a cachestore flush of ‘Object Plans‘, ‘SQL Plans‘ and ‘Bound Trees‘ has completed, the property box will finally close.

Click to enlarge.
As per the above screenshot, this took well over 30 minutes for this VM which was placed on an over provisioned host.

Leave a Reply