[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
On Monday 06 October 2008 22:58, Kevin Tunison wrote: > Hi List, > > More and more frequently over the past several months I have been involved > with an increasing number of virtualization products. Particularly VMWare > based. I would like to ask if any members here have any preferences or > caveats when it comes to choosing a bare-metal virtualization solution. I > have pretty much ruled out Microsofts Hypervisor because of their storage > setup limitations. Has anyone had any experience with XenSource, Xen, > Sun's Logical domains (despite the flamewar on bugtraq), or ESX with any > production high I/O SQL databases (like, say 100-750GB dbs with 10-100GB of > daily data change)? > > One of the companies I work for uses several different dbs, one of them > being SQL Server. For me, this has harranged a choice in VMWare as they > only explicitly support OS's, not applications. Has anyone come across any > political hang-ups when it comes to virtualization technology because it > doesn't explicitly support a particular database? What was done and how > was the outcome? Also, I notice that Microsoft has changed their licensing > structure to be particularly detrimental to the widescale adoption of > VMWare ESX with MS non-OS products. It would be nice to know if anyone has > had success in requesting support for SQL server on a virtualization > platform. I feel that the last thing MS is going to do is to help make its products work over virtualisation. It may even force an ISO self contradictory standard to confuse the gullible. IMHO virtualisation is barking in the wrong forest for non ISO developers. Sensible software design should mean moving OS/Server/Dbase etc amongst machines and OS's is relatively simple. I think virtualisation will be looked on a bit like office software is starting to be seen now - an oxbow lake in the stream of IT development. It could be useful IF MS played but I don't ever see that happening so its never going to do what it says on the box. If you, or your clients have to use SQL server then I suggest they host in on an MS machine and access it using one of the many network accessing drivers available and experiment with transferring the db system to another open DB before MS do something really silly with it. Tom te tom te tom -- The Mailing List for the Devon & Cornwall LUG http://mailman.dclug.org.uk/listinfo/list FAQ: http://www.dcglug.org.uk/linux_adm/list-faq.html