Unanswered: Virtualize SQL 2005 on Hyper-V not recommended? Must use SQL 2008?
I was told by someone that visualizing SQL 2005 on Hyper-V is not recommended. I can't remember the details but I was told that if there is any power failure during the transaction commit, the VMs may be informed that the commit is completed but in actual fact, the commit at disk level may not be done. SQL 2008 overcome this by ensuring the commit is completed at disk level b4 telling the VMs that it's done.
May I know if that's true? I tried searching from the net but couldn't get much info about this....what is that particular thing on SQL 2005 that's not reporting the right status?