I already have a SQL active/pasive cluster running 2008 for both OS and SQL. I am going to implement a Hyper-V cluster for several of my applications and was wondering about SQL. I have read that SQL high availability is not supported under Hyper-V, so I'm wondering which way to go. My SQL will house databases for Microsoft OCS, my antivirus software, and I had planned on creating another SQL instance for Sharepoint (following best practices) or I could just load another VM of SQL.
So would I have one SQL server under the Hyper-V cluster and get my redundancy that way, or have 2 SQL servers in a high availability cluster like I have now? Any thoughts or suggestions?
So would I have one SQL server under the Hyper-V cluster and get my redundancy that way, or have 2 SQL servers in a high availability cluster like I have now? Any thoughts or suggestions?