The official SQL Server AlwaysOn team blog.
Newly published: two new architecture guides:
These two new guides, along with the one published earlier on Multi-site FCIs (http://download.microsoft.com/download/D/2/0/D20E1C5F-72EA-4505-9F26-FEF9550EFD44/SQLServer2012_MultisiteFailoverCluster%20(2).docx) complete the series of AlwaysOn HA/DR architectures and design patterns (http://blogs.msdn.com/b/sqlalwayson/archive/2012/01/27/now-available-microsoft-sql-server-alwayson-solutions-guide-for-high-availability-and-disaster-recovery.aspx).
No pedo continuar por mi vista pues me esta haciendo daño el refle...de la pantallla.
Have you seen the AlwaysOn Availability Groups synchronous latencies with/out SSDs in the solution? I see comments from some who attended the recently concludd SQLPASS conf. that nobody talked about Sync, but only ASync due to significant performance degradation when using Sync. Is that true?
Also, if 3 nodes (2sync + 1Async) were used in the PRIMARY and 2Async in the DR site - where should one host the Domain Controller as the setup requires all nodes in be in a single cluster and same domain.