Such were problems with getting Windows Failover Clustering to work, I had keep troubleshooting it on the backburner whilst I worked on learning something new.I couldn’t allow my problems with Failover Clustering to hold me back.
In Azure, the usual way to increase throughput for SQL Server OLTP workloads is striping premium storage disks together in order to aggregate their IOPS & bandwidth.
By properly configuring Storage Spaces in combination with Azure Premium Storage you can achieve up to 80.000 IOPS and 2.000 MB/sec throughput for a single GS5 virtual machine, see here.
Although MSCS is an extremely immature product it is expected to play a key role in analyst’s predictions that NT will surpass UNIX as the universal NOS of choice.
It’s been brought to my attention that I might have been a little “harsh” on Microsoft’s validation tool.
‘Hang on’, you might say, ‘doesn’t FCI require shared storage – is that possible at all in Azure?
’ Actually it is, by leveraging SIOS Data Keeper from the Azure Marketplace in order to synchronize local disks attached to the cluster nodes.Audience: XMPie customers who have SQL server Standard Edition and wish to create a failover SQL cluster configuration.It is the full responsibility of the IT department to configure the SQL failover configuration.I guess its up to the administrator to interpret these warnings and decide if they are show stops or not.The other thing that’s become apparent is the validation tool itself hasn’t been recently update to reflect Windows Hyper-V 2012 native support for NIC teaming. The post was actually written before I started using the SCVMM “Logical Switch” as such it makes references to Standard Switches and the NIC Teaming available at the Windows Hyper-V.XMPie does not provide support for this process, nor is XMPie liable in any way for its results.