• Grant Fritchey - Monday, April 3, 2017 2:43 AM

    OK. So you have 16gb of memory. You can't allocate all of it to the VMs. You have to have memory left behind on the physical box to ensure there's memory there for managing the OS and the hypervisor. If you do attempt this, what happens is that you start getting all sorts of swapping of memory pages out to disk. This is a bad situation. Instead, drop down to about 14gb and allocate 7gb to each SQL Server instance. Then go from there.

    Is this meant to be a production server? If so, 16gb is exceedingly tiny. My tablet-style laptop has 16gb of memory. I wouldn't attempt to run a production load on the system.

    Thanks for contributing Grant, I read a lot of your published material. I said I had 2 VM's @ 8GB each - I do not run these simultaneously but one at the time always reserving <=8GB to the host. It is not a production server but a learning environment on ThinkPad. My confusion is the seeming differential between what Hyper-V manager says is allocated to the VM and what the VM utilization seems to be via task manager- that is I know I'm not using 90% of 8GB with just SSMS open.

    _____________________________________________________________________
    As soon as you see something, you already start to intellectualize it. As soon as you intellectualize something, it is no longer what you saw. Suzuki-roshi