Image from: https://learn.microsoft.com/en-us/azure/azure-sql/virtual-machines/windows/availability-group-overview Edited July 2 2022 after reviewing my Facebook discussion with Eugene Sergeev on Microsoft’s product team. MIM 2016 SP2 (and 4.4.1459.0 or later supports SQL Server Always On Availability Groups (AG))! Yeah! Ok let’s implement it! But wait! It won’t give us all we hope for! Up to the moment distributed backup of the data – yes! Automatic instant failover – not without a huge caveat! What do you mean it won’t give us Automatic Instant Failover?
David, I can’t figure this one out easily s… Anu - Mar 1, 2009David, I can’t figure this one out easily since I don’t have a deep knowledge of SQL. I’d appreciate your feedback. I am beginning to understand the different options and implementaions for scaling out SQL HA/DR/automatic failover. In ILM “2” architecture, with scaling out MIIS and its SQL, can performace improvements and concurrent MA runs be achieved? I think not but I’d like to wrong this time!
First, let me say thank you to Alex Tcherniakhovski for pioneering the way in clustering the MIIS Service or as it is now known the ILM Sync Engine. That blog, presentation and script was an excellent set of work. http://blogs.msdn.com/alextch/archive/2005/12/17/clusteredmiis.aspx On Windows Server 2008, a few things have changed that break the script that Alex T. provides. In Windows Server 2003 the cluster services runs as a domain account and as long as the user has access to all nodes, to stop and start services, and as an MIIS Administrator then it should be able to do the trick.