AWS prescriptive-guidance documentation change
Summary
Updated introduction link, added detailed migration workflow with diagram, distributed availability group references, and clarified downtime options. Removed redundant content.
Security assessment
Changes enhance migration guidance documentation without addressing security vulnerabilities or introducing security features. Added content focuses on high availability architecture and migration procedures, not security controls or vulnerabilities.
Diff
diff --git a/prescriptive-guidance/latest/migration-sql-server/always-on.md b/prescriptive-guidance/latest/migration-sql-server/always-on.md index 24c83fab4..b31513310 100644 --- a//prescriptive-guidance/latest/migration-sql-server/always-on.md +++ b//prescriptive-guidance/latest/migration-sql-server/always-on.md @@ -5 +5 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Migrating Microsoft SQL Server databases to the AWS Cloud](welcome.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Migrating Microsoft SQL Server databases to the AWS Cloud](introduction.html) @@ -9 +9,17 @@ -SQL Server Always On availability groups is an advanced, enterprise-level feature to provide high availability and disaster recovery solutions. This feature is available if you are using SQL Server 2014 and later versions. You can also use an Always On availability group to migrate your on-premises SQL Server databases to Amazon EC2 on AWS. This approach enables you to migrate your databases with minimal to no downtime. +SQL Server Always On availability groups is an advanced, enterprise-level feature to provide high availability and disaster recovery solutions. This feature is available if you are using SQL Server 2014 and later versions. You can also use an Always On availability group to migrate your on-premises SQL Server databases to Amazon EC2 on AWS. This approach enables you to migrate your databases either with downtime or with minimal downtime. + +If you have an existing on-premises deployment of SQL Server Always On availability groups, your primary replica and secondary replica will be synchronously replicating data within the availability group. So, to migrate your database to the AWS Cloud, you can extend your Windows Server Failover Clustering (WSFC) cluster to the cloud. This can be temporary, just for migration purposes. You then create a secondary replica in the AWS Cloud and use asynchronous replication, as shown in the following diagram. After the secondary replica is synchronized with the primary on-premises database, you can perform a manual failover whenever you are ready for cutover. + + + +###### Note + +At any given point of time, there is only one database that is available for write operations. You can use the remaining secondary replicas for read operations. To scale out your read workloads, you can add more read replicas in multiple Availability Zones on AWS. + +For more information about distributed availability groups, see: + + * [Microsoft SQL Server documentation](https://docs.microsoft.com/en-us/sql/database-engine/availability-groups/windows/distributed-availability-groups), + + * [How to architect a hybrid Microsoft SQL Server solution using distributed availability groups](https://aws.amazon.com/blogs/database/how-to-architect-a-hybrid-microsoft-sql-server-solution-using-distributed-availability-groups/) on the AWS Database blog + + * [Migrate SQL Server to AWS using distributed availability groups](https://docs.aws.amazon.com/prescriptive-guidance/latest/patterns/migrate-sql-server-to-aws-using-distributed-availability-groups.html) on the AWS Prescriptive Guidance website @@ -11 +26,0 @@ SQL Server Always On availability groups is an advanced, enterprise-level featur -If you have an existing on-premises deployment of SQL Server Always On availability groups, your primary replica and secondary replica will be synchronously replicating data within the availability group. So, to migrate your database to AWS Cloud, you can extend your Windows Server Failover Clustering (WSFC) cluster to the cloud. This can be temporary, just for migration purposes. You then create a secondary replica in the AWS Cloud and use asynchronous replication, as shown in the following diagram. After the secondary replica is synchronized with the primary on-premises database, you can perform a manual failover whenever you are ready for cutover. @@ -13 +27,0 @@ If you have an existing on-premises deployment of SQL Server Always On availabil - @@ -15 +28,0 @@ If you have an existing on-premises deployment of SQL Server Always On availabil -For more information about using this method to achieve high availability, data protection, and disaster recovery for your SQL Server databases on Amazon EC2, see [Always On availability groups](./ec2-always-on.html) in the _Amazon EC2 for SQL Server_ section.