nav-img
Advanced

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.
  • After you change instance classes, the DB instances will be rebooted and service will be interrupted. Therefore, you are advised to change instance classes during off-peak hours.

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service.
  4. 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 name to go to the Basic Information page. In the DB Information area, click Change next to the Instance Class field.

  5. On the displayed page, specify the new instance class and click Next.
  6. Check the change result.

    Changing the DB instance class takes 5–15 minutes. During this period, the status of the DB instance on the Instances page is Changing instance class. After a few minutes, click the DB instance and view the instance class on the displayed Basic Information page to check that the change is successful.

    Notice

    After you change the instance class of an RDS for SQL Server instance, the value of max server memory will be changed accordingly. You are advised to set max server memory to Memory size (GB) x 1024 x 0.85 – 1.5 x 1024. For example, if your memory is 4 GB, set max server memory to 1946 MB (4 x 1024 x 0.85-1.5 x 1024).