You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+7-6Lines changed: 7 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,10 +30,10 @@ The database is migrated using AWS DMS. It continuously synchronises changes in
30
30
31
31
#### Summary
32
32
33
-
This sample will deploy the two SQL Server instances (one EC2 and one Amazon RDS) in their own VPCs.
34
-
The SQL Server running in the EC2 instance represents the on-premises infrastructure and the Amazon RDS instance represents,
35
-
then create a sample database in both. No tables will be created at this point - creating of tables inside the database is left to the user.
36
-
A DMS migration task will also be created. Upon starting that task (eg; using console or aws cli), tables in the database will be continually replicated across from the EC2 instance to the Amazon RDS instance.
33
+
This sample will deploy two SQL Server instances, one on EC2 and one on Amazon RDS, in their own VPCs.
34
+
The SQL Server running on the EC2 instance represents the on-premises infrastructure, and the Amazon RDS instance represents AWS cloud.
35
+
No tables will be created at this point - creating of tables inside the database is left to the user.
36
+
AWS DMS migration task will also be created. Upon starting that task (eg; using console or aws cli), tables in the database will be continually replicated across from the EC2 instance to the Amazon RDS instance.
37
37
38
38
### Architecture
39
39
@@ -83,6 +83,7 @@ template are pre-populated. Click the *Next* button at the bottom of the page.
83
83
|---------------|-------|-----------|
84
84
|Availability Zones|Requires input|The list of Availability Zones to use for the subnets in the VPCs. *Use two AZs*.|
85
85
|On premise CIDR IP|Requires input|The CIDR Allowed RDP and SQL access to the EC2 and RDS host. CIDR block parameter must be in the form x.x.x.x/0-32.|
86
+
|DMSInstanceClass|dms.t3.large|Instance class of DMS instance.|
86
87
|EC2 instance type|m5.2xlarge|The EC2 instance type for Microsoft SQL server.|
87
88
|Windows server AMI|/aws/service/ami-windows-latest/Windows_Server-2019-English-Full-SQL_2016_SP2_Standard|Query for the Latest Windows AMI Using Systems Manager Parameter Store https://aws.amazon.com/blogs/mt/query-for-the-latest-windows-ami-using-systems-manager-parameter-store/|
88
89
|MSSQL Server version|13|MSSQL Server version. This is used to Change Auth mode from Windows only to SQL and Windows Auth. For MSSQL server 2017 use number 14, for MSSQL server 2016 use number 13.|
@@ -111,7 +112,7 @@ template are pre-populated. Click the *Next* button at the bottom of the page.
111
112
[Database guide](docs/database/README.md)
112
113
113
114
### Limitations
114
-
- MSSQL server 2017 doesnt support continues replication. The solution is using MSSQL server 2016 by default.
115
+
- MSSQL server 2017 doesn't support continues replication. The solution is using MSSQL server 2016 by default.
115
116
116
117
## Local Development
117
118
See [Local Development](docs/LOCAL_DEVELOPMENT.md) guide to get a copy of the project up and running on your local machine for development and testing purposes.
@@ -123,7 +124,7 @@ To remove the stack:
123
124
1. Open the AWS CloudFormation Console
124
125
1. Click the *aws-dms-sql-server* project, right-click and select "*Delete Stack*"
125
126
1. Your stack will take some time to be deleted. You can track its progress in the "Events" tab.
126
-
1. When it is done, the status will change from DELETE_IN_PROGRESS" to "DELETE_COMPLETE". It will then disappear from the list.
127
+
1. When it is done, the status will change from "DELETE_IN_PROGRESS" to "DELETE_COMPLETE". It will then disappear from the list.
0 commit comments