none
Windows cluster sql server 2012 RRS feed

  • Question

  • We are looking at creating a Windows 2012 cluster that we will use for SQL server 2012.  All I have read is that "At this time, CSVs do not support the Microsoft SQL Server clustered workload."  What is the optimal storage solution if CSV's are not an option?

    Thanks

    Tuesday, October 1, 2013 2:17 PM

Answers

  • You can use CSVs for Hyper-V, then run SQL Server in a VM.  This will give you the ability to do live migration, Hyper-V replication and run other VMs on that cluster.  

    Or you can install SQL directly on the cluster nodes as a Failover Cluster Instance using shared storage.  The shared disks aren't CSVs, but the cluster will move the disks to whichever node hosts the Failover Cluster Instance.

    David


    David http://blogs.msdn.com/b/dbrowne/

    Tuesday, October 1, 2013 2:22 PM
  • A CSV is a way to share a LUN between hosts.  Your VMs will use VHDX files as their virtual disks.  If you have enough disks, then you can use separate CSVs for OS, SQL Data, TempDb and Log.  If you don't then you can configure separate VHDXs for each of these and put them all on the same CSV.  You can later move them to different CSVs.

    David


    David http://blogs.msdn.com/b/dbrowne/

    Tuesday, October 1, 2013 4:29 PM

All replies

  • You can use CSVs for Hyper-V, then run SQL Server in a VM.  This will give you the ability to do live migration, Hyper-V replication and run other VMs on that cluster.  

    Or you can install SQL directly on the cluster nodes as a Failover Cluster Instance using shared storage.  The shared disks aren't CSVs, but the cluster will move the disks to whichever node hosts the Failover Cluster Instance.

    David


    David http://blogs.msdn.com/b/dbrowne/

    Tuesday, October 1, 2013 2:22 PM
  • Thanks for the information.  Do you know if there is documentation on
    that?  We are working on a server now that we are going to make a
    Hyper-V and create 2 test VM's that will eventually have SQL server.

    Would the CSV be on one single LUN?  Or is it best to carve separate ones?

    Tuesday, October 1, 2013 3:50 PM
  • A CSV is a way to share a LUN between hosts.  Your VMs will use VHDX files as their virtual disks.  If you have enough disks, then you can use separate CSVs for OS, SQL Data, TempDb and Log.  If you don't then you can configure separate VHDXs for each of these and put them all on the same CSV.  You can later move them to different CSVs.

    David


    David http://blogs.msdn.com/b/dbrowne/

    Tuesday, October 1, 2013 4:29 PM