Changing a DB Instance Class

Scenarios

You can change the instance class (vCPU or memory) of a DB instance as required. If the status of a DB instance changes from Changing instance class to Available, the change is successful.

Constraints

• An instance cannot be deleted while its instance class is being changed.
• The following operations cannot be performed on an instance whose instance class is being changed: rebooting the instance, scaling up storage space, modifying the parameter template, creating a manual backup, creating a database account, and creating a database.
• After you change instance classes, the DB instances will reboot and services will be interrupted. Therefore, you are advised to change instance classes during off-peak hours.
• Changing the instance class takes 5 to 15 minutes. Service downtime only occurs during the primary/standby switchover.

Procedure

1. Log in to the management console.
2. Click in the upper left corner of the page and choose Databases > Relational Database Service.
3. On the Instances page, locate the target DB instance and choose More > Change Instance Class in the Operation column.

   Alternatively, click the target DB instance to go to the Basic Information page. In the DB Information area, click Change next to the Instance Class field.

4. On the displayed page, specify the new instance class and click Next.
5. Confirm the specifications.
   • If you need to modify your settings, click Previous.
   • For pay-per-use DB instances, click Submit.

6. View the DB instance class change result.

   Return to the Instances page and view the instance status. During the change period, the instance status is Changing instance class. After a few minutes, view the DB instance class on the Basic Information page to check that the change is successful.