SQL Server High Availability best practices [AX 2012]
Updated: August 20, 2013
Applies To: Microsoft Dynamics AX 2012 R3, Microsoft Dynamics AX 2012 R2
If Microsoft SQL Server high availability services such as failover clustering, mirroring, or log shipping are running in your environment, consider the following best practices:
Set up high availability only in your production environment.
Disable any high availability service when you perform any operations that might change the database structure and require synchronization. For example, disable log shipping when you apply updates, or when you synchronize the database so that it includes changes from the Application Object Tree (AOT).
For detailed recommendations on how to set up a Microsoft Dynamics AX system for high availability, see SQL Server topology recommendations for availability and performance.
Announcements: To see known issues and recent fixes, use Issue search in Microsoft Dynamics Lifecycle Services (LCS).