Content

Target customers: SQL Server users and users that have read/write splitting requirements for databases. This will require the separation of read requests using read-only instances in multiple scenarios, such as data collection and analysis, and load balancing of intense/high traffic. You must first purchase SQL Server 2017 Enterprise Edition AlwaysOn instances. Then, you can purchase read-only instances as required. The underlying AlwaysOn architecture implements control over clusters, such as automatic data replication, load balancing among read-only instances, and failover between primary and secondary instances. Versions and specifications: 1. The underlying engine of RDS for SQL Server is Microsoft SQL Server 2017 Enterprise Edition. You can deploy the data engine with the AlwaysOn technology to implement the read/write splitting architecture. 2. With RDS for SQL Server AlwayOn, you can create up to seven read-only instances. Each read-only instance has its own endpoint. You can apply for a unified endpoint for all read-only instances to implement load balancing between multiple instances. 3. An SQL Server AlwaysOn instance supports a specification of up to 64 CPUs and 512 GB memory. You must first purchase SQL Server 2017 Enterprise Edition AlwaysOn instances. Then, you can purchase read-only instances as required. The underlying AlwaysOn architecture implements control over clusters, such as automatic data replication, load balancing among read-only instances, and failover between primary instances and secondary instances. 4. The billing method for read-only instances is Pay-As-You-Go. You can stop these instances at any time to facilitate the management of instances based on business traffic. This provides you with a cost-effective cluster configuration.