- Documentation
RDS for SQL Server
User guide
Managing read-only instance
View the connection address of a read-only instance.
Managing read-only instance
View the connection address of a read-only instance.
View the connection address of a read-only instance.
RDS for SQL Server supports the creation of read-only instances to offload read pressure from the primary instance. It also provides a unified read-only cluster connection address to help you manage these instances. You can configure the primary instance and unified read-only cluster connection addresses in your application to reduce read pressure on the primary instance and improve the system's overall processing capability.
Description
To reduce read pressure on the primary instance, RDS for SQL Server provides the following two types of connection addresses for read-only instances:
- A unified read-only cluster connection address for multiple read-only instances: The system provides a unified connection address on the primary instance's connection management tab for all of its read-only instances. This is the connection address of the read-only cluster endpoint. If you configure this read-only address in your application, the system evenly distributes all read requests across all read-only instances.
- A connection address for each read-only instance: The system provides a connection address for each read-only instance on its own connection management tab. If you configure the connection address of a single read-only instance in your application, the system directs all read requests to that specific read-only instance.
Prerequisites
A primary RDS for SQL Server instance and read-only instances have been created, and the primary instance must meet the following conditions.
- Compatible versions: SQL Server 2019 Enterprise Edition, SQL Server 2022 Enterprise Edition.
Precautions
- After you create read-only instances, the system creates a unified read-only cluster endpoint for them by default. The unified read-only cluster endpoint address is fixed and does not change when you add or delete read-only instances. This eliminates the need to repeatedly modify your application, reducing maintenance costs.
- After you create read-only instances, the system creates a separate read-only node endpoint for each one by default.
- Read-only addresses are free. You are only charged for the read-only instances.
Procedure
View the unified connection address for multiple read-only instances
tip
The Connection Management tab for the primary instance displays the unified read-only cluster connection address, which is the connection address for the read-only cluster endpoint.
- In the upper-left corner of the top menu bar, select the project and region of the instance.
- In the left navigation bar, click Instances.
- On the Instances page, click the name of the primary instance for the target read-only instance.
- On the Instance information page of the target instance, click Connection management.
- In the Connection topology area of the Connection management tab, hover over the Read-only cluster endpoint card.
- The pop-up window displays the unified private connection address and port for all read-only instances of the current primary instance.
View the connection address of a single read-only instance
- In the upper-left corner of the top menu bar, select the project and region of the instance.
- In the left navigation bar, click Instances.
- On the Instances page, click the plus icon before the target instance name, and then click the name of the target read-only instance.
- On the Instance information page of the target read-only instance, click Connection management.
- On the Connection management tab, in the Connection topology area, hover over the Read-only node endpoint card.
- In the pop-up window, you can view the private network address, public network address, and port of the read-only instance.
Last updated: 2026.01.29 16:48:28