Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Is it good practice to have the database of an application on the same physical server as the application but separated by a virtual machine?

share|improve this question

It seems reasonable enough as long as there is enough resource - for the database server, be especially careful not to overcommit memory or CPU, and ensure that memory doesn't use the balloon driver.

share|improve this answer
Ignore memory and CPU ;) THe most likely overload candidate is IO - "the server has 2 dsics" instead of 20 ;) – TomTom Jan 9 '12 at 17:55
Hi TomTom, how do you know? – Chopper3 Jan 9 '12 at 18:18
Databases are disc IO intensive, but when virtualising we mitigate this by throwing memory at the problem. – Peter Schofield Jan 9 '12 at 20:09

"Good Practice" - personally I don't like running production DBs in VMs but if you want to do that then actually running them on the same host would be great as your virtual networking between the two would be FAR quicker than any regular physical networking available.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.