This topic describes how to manually release a pay-as-you-go-billed ApsaraDB RDS for SQL Server instance or unsubscribe from a subscription-billed ApsaraDB RDS for SQL Server instance.
Precautions
- After you release or unsubscribe from an RDS instance, the RDS instance and its data are immediately deleted. Before you release or unsubscribe from an RDS instance, we recommend that you back up the RDS instance and download the required backup file.
- If you want to release the last read-only RDS instance that is attached with a primary RDS instance, you must disable the read/write splitting function for the primary RDS instance. For more information, see Disable the read-only routing endpoint of an ApsaraDB RDS for SQL Server instance.
Release a pay-as-you-go-billed RDS instance
Unsubscribe from a subscription RDS instance
If you want to unsubscribe from an RDS instance, submit a ticket.
FAQ
If I release a read-only RDS instance, will my workloads be interrupted?
Yes, if you release a read-only RDS instance, your workloads on the read-only instance
will be interrupted. Before you release a read-only RDS instance, we recommend that
you set the read weight of the read-only RDS instance to 0.
Note The cached connections with the read-only RDS instance that you have released remains
valid. You must close these connections and establish new connections.
Related operations
Operation | Description |
---|---|
Release instance | Releases a pay-as-you-go ApsaraDB RDS instance. You cannot unsubscribe from a subscription ApsaraDB RDS instance by calling an API operation. |