It is definitely at the virtualization level. I already sent a MSG to the venefax suggesting that he should drop virtualization on his 200k a day production system. Obviously, the choice of xen is not optimal. Combine it with windows server os, all hell breaks loose. For 72 million dollar a year revenue system, it is a lot safer and stable to have redundant physical servers anyways. It is not really wise to try to consolidate to save electricity to introduce single point of failures, let alone software driver crashing at the virtualization layer.
This whole thing smells like an internal blame game. I would have fired anyone who suggests virtualization on production servers that introduced single point of failure on a critical service. WOW, this is funny cause it sounds like you already have, it might not have been at the database level but it sure was at the virtualization level On Mon, Jul 21, 2008 at 9:30 AM, Fajar A. Nugraha < fajar@xxxxxxxxx> wrote:
Venefax wrote:
SQL Server only runs in Windows. I am now actually learning DB2 in order to
use a Linux-based database. But of course I am not dumb to put my entire
business on a database I cannot support, yet, the way I do with SQL Server.
And the beauty is the with XEN-Windows 2008, SQL Server runs perfectly,
unless Windows crashes.
|
