One of our DBAs posed a question - under normal load, SQL Server will take as much memory as the VM it's running on has been allocated (say 4GB). It will ring fence this. They suggest it would be very bad if ESX came along and tried to reclaim the memory and the question that arose was, does ESX only try to reclaim memory that hasn't been accessed recently?
If so, does the fact that SQL Server has ring-fenced the memory but may not be actively using it make ESX think it's not being used and reclaim it? This would be bad for SQL server and have a real impact on its performance.
Any thoughts (feel free to correct me if I've not got something straight or have made some bogus assumptions).
Regards
Jon