yexinru/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity
Files
ac787f42f1e2d2e611f07a75624c4380a68149aa
doc-exports/docs/rds/umn/rds_mssql_start.html
wangdengke2 64672e58fb rds_umn 
Reviewed-by: Wagner, Fabian <fabian.wagner@t-systems.com>
Co-authored-by: wangdengke2 <wangdengke2@huawei.com>
Co-committed-by: wangdengke2 <wangdengke2@huawei.com>
2025-09-19 08:45:25 +00:00

3.4 KiB
Raw Blame History

Starting a DB Instance

Scenarios

You can stop your instance temporarily to save money. After stopping your instance, you can restart it to begin using it again.

Billing

After a DB instance is started, the VM where the DB instance is located is billed again.

Constraints

  • If you start a primary instance, read replicas (if there are any) will also be started.
  • When a stopped DB instance is started, a full backup is automatically triggered.
  • Only instances in Stopped state can be started.

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 primary instance that you want to start and choose More > Start in the Operation column.
  5. In the displayed dialog box, click Yes.
  6. Refresh the instance list and view the status of the instance. If the status is Available, the instance is started successfully.
Parent topic: Instance Lifecycle