ApsaraDB RDS allows you to read data from secondary RDS instances of their primary ApsaraDB RDS for SQL Server instances that run RDS Cluster Edition. This topic describes how to configure the read attribute for a secondary RDS instance of a primary RDS instance. By default, after you create a primary RDS instance that runs RDS Cluster Edition, you can read data from the secondary RDS instance of the primary RDS instance. The secondary RDS instance serves as a read-only RDS instance, which reduces the cost of cloud migration.

Prerequisites

Functionality

  • After you create an RDS instance that runs RDS Cluster Edition, a primary RDS instance and a secondary RDS instance are provisioned. By default, the secondary RDS instance is read-only. Therefore, the secondary RDS instance can serve as a read-only instance.
  • After the read/write splitting feature is enabled for the primary RDS instance, you can configure read weights for the primary, secondary, and read-only RDS instances. For more information, see Procedure.
  • If an existing primary RDS instance runs RDS Cluster Edition and the read/write splitting feature is enabled for the primary RDS instance, you can directly read data from the secondary RDS instance of the primary RDS instance. If the read/write splitting feature is disabled, you must enable the feature and configure a read-only routing endpoint. For more information, see Procedure.

Procedure

  1. Access RDS Instances, select a region at the top, and then click the ID of the target RDS instance.
  2. In the left-side navigation pane, click Cluster management.
  3. On the page that appears, click Configure Readonly Splitting Address next to Basic Information to configure read weights.

Related operations

Operation Description
AllocateReadWriteSplittingConnection Applies for a read-only routing endpoint for a primary ApsaraDB RDS instance.