Updated on 2022-08-16 GMT+08:00

Step 1: Create a DB Instance

Scenarios

This section describes how to create a DB instance on the RDS console.

The DB instance class and storage space you need depend on your processing power and memory requirements.

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. The RDS console is displayed.
  4. On the Instance Management page, click Create DB Instance.
  5. On the displayed page, configure information about your DB instance. Then, click Create Now.

    Table 1 Basic information

    Parameter

    Description

    Region

    The region where your RDS resources will be located. You can change it on the creation page, or go back to the Instance Management page and change it in the upper left corner.

    NOTE:

    Products in different regions cannot communicate with each other through a private network and you cannot change the region of a DB instance after creating the instance. Therefore, exercise caution when selecting a region.

    DB Instance Name

    Must start with a letter and consist of 4 to 64 characters. Only letters, digits, hyphens (-), and underscores (_) are allowed.

    DB Engine

    Set to Microsoft SQL Server.

    DB Engine Version

    For details, see DB Engines and Versions.

    Different DB engine versions are supported in different regions.

    You are advised to select the latest available version because it is more stable, reliable, and secure.

    DB Instance Type

    • Primary/Standby: uses an HA architecture with a primary DB instance and a synchronous standby DB instance. It is suitable for production databases of large- and medium-sized enterprises in Internet, Internet of Things (IoT), retail e-commerce sales, logistics, gaming, and other sectors. The standby DB instance improves instance reliability and is invisible to you after being created.

      An AZ is a physical region where resources use independent power supply and networks. AZs are physically isolated but interconnected through an internal network.

      You can deploy primary and standby DB instances in a single AZ or across AZs to achieve failover and high availability.

    • Single: uses a single-node architecture, which is more cost-effective than primary/standby DB instances. It is suitable for development and testing of microsites, and small- and medium-sized enterprises, or for learning about RDS.

    Storage Type

    Determines the DB instance read/write speed. The higher the maximum throughput is, the higher the DB instance read/write speed can be.

    • High I/O: supports a maximum throughput of 150 MB/s.
    • Ultra-high I/O: supports a maximum throughput of 350 MB/s.

    Time Zone

    Select your time zone when you are creating a DB instance. After the DB instance is created, the time zone cannot be modified.

    Server Collation

    Defines a collation of a database or table column, or a collation cast operation when applied to character string expression. It acts as the default collation for the DB instance.

    Table 2 Mapping between time zones and UTC offsets

    Time Zone

    Standard Time Offset

    Remarks

    Afghanistan Standard Time

    UTC+04:30

    Kabul

    Alaskan Standard Time

    UTC-09:00

    Alaska

    Arabian Standard Time

    UTC+04:00

    Abu Dhabi, Muscat

    Atlantic Standard Time

    UTC-04:00

    Atlantic Time (Canada)

    AUS Central Standard Time

    UTC+09:30

    Darwin

    AUS Eastern Standard Time

    UTC+10:00

    Canberra, Melbourne, Sydney

    Belarus Standard Time

    UTC+03:00

    Minsk

    Canada Central Standard Time

    UTC-06:00

    Saskatchewan

    Cape Verde Standard Time

    UTC-01:00

    Cape Verde Is.

    Cen. Australia Standard Time

    UTC+09:30

    Adelaide

    Central America Standard Time

    UTC-06:00

    Central America

    Central Asia Standard Time

    UTC+06:00

    Astana

    Central Brazilian Standard Time

    UTC-04:00

    Cuiaba

    Central European Standard Time

    UTC+01:00

    Belgrade, Bratislava, Budapest, Ljubljana, Prague

    Central European Standard Time

    UTC+01:00

    Sarajevo, Skopje, Warsaw, Zagreb

    Central Pacific Standard Time

    UTC+11:00

    Solomon Islands, New Caledonia

    Central Standard Time

    UTC-06:00

    Central Time (US and Canada)

    China Standard Time

    UTC+08:00

    Beijing, Chongqing, Hong Kong, and Urumqi

    E. Africa Standard Time

    UTC+03:00

    Nairobi

    E. Australia Standard Time

    UTC+10:00

    Brisbane

    E. Europe Standard Time

    UTC+02:00

    Chisinau

    E. South America Standard Time

    UTC-03:00

    Brasilia

    Eastern Standard Time

    UTC-05:00

    Eastern Time (US and Canada)

    Georgian Standard Time

    UTC+04:00

    Tbilisi

    GMT Standard Time

    UTC

    Dublin, Edinburgh, Lisbon, London

    Greenland Standard Time

    UTC-03:00

    Greenland

    Greenwich Standard Time

    UTC

    Monrovia, Reykjavik

    GTB Standard Time

    UTC+02:00

    Athens, Bucharest

    Hawaiian Standard Time

    UTC-10:00

    Hawaii

    India Standard Time

    UTC+05:30

    Chennai, Kolkata, Mumbai, New Delhi

    Jordan Standard Time

    UTC+02:00

    Amman

    Korea Standard Time

    UTC+09:00

    Seoul

    Middle East Standard Time

    UTC+02:00

    Beirut

    Mountain Standard Time

    UTC-07:00

    Mountain Time (US and Canada)

    US Mountain Standard Time

    UTC-07:00

    Arizona

    New Zealand Standard Time

    UTC+12:00

    Auckland, Wellington

    Newfoundland Standard Time

    UTC-03:30

    Newfoundland

    Pacific SA Standard Time

    UTC-03:00

    Santiago

    Pacific Standard Time

    UTC-08:00

    Pacific Time (US and Canada)

    Russian Standard Time

    UTC+03:00

    Moscow/St. Petersburg

    SA Pacific Standard Time

    UTC-05:00

    Bogota, Lima, Quito, Rio Branco

    SE Asia Standard Time

    UTC+07:00

    Bangkok, Hanoi, Jakarta

    China Standard Time

    UTC+08:00

    Kuala Lumpur, Singapore

    Tokyo Standard Time

    UTC+09:00

    Osaka, Sapporo, Tokyo

    US Eastern Standard Time

    UTC-05:00

    Indiana (East)

    UTC

    UTC

    Coordinated Universal Time

    UTC-02

    UTC-02:00

    Coordinated Universal Time–02

    UTC-08

    UTC-08:00

    Coordinated Universal Time–08

    UTC-09

    UTC-09:00

    Coordinated Universal Time–09

    UTC-11

    UTC-11:00

    Coordinated Universal Time–11

    UTC+12

    UTC+12:00

    Coordinated Universal Time+12

    W. Australia Standard Time

    UTC+08:00

    Perth

    W. Central Africa Standard Time

    UTC+01:00

    West Central Africa

    W. Europe Standard Time

    UTC+01:00

    Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna

    Table 3 Instance specifications

    Parameter

    Description

    Instance Class

    Refers to the CPU and memory of a DB instance. Different instance classes have different numbers of database connections and different maximum IOPS.

    For details about instance classes, see DB Instance Classes.

    After a DB instance is created, you can change its CPU and memory. For details, see Changing a DB Instance Class.

    Storage Type

    Determines the DB instance read/write speed. The higher the maximum throughput is, the higher the DB instance read/write speed can be.

    • High I/O: supports a maximum throughput of 150 MB/s.
    • Ultra-high I/O: supports a maximum throughput of 350 MB/s.

    Storage Space (GB)

    Contains the file system overhead required for inode, reserved block, and database operation. Storage space can range in size from 40 GB to 4,000 GB and can be scaled up only by a multiple of 10 GB.

    After a DB instance is created, you can scale up its storage space. For details, see section Scaling up Storage Space.

    Table 4 Network

    Parameter

    Description

    VPC

    A dedicated virtual network in which your RDS DB instances are located. A VPC can isolate networks for different services. You can select an existing VPC or create a VPC. For details on how to create a VPC, see the "Creating a VPC" section in the Virtual Private Cloud User Guide.

    If no VPC is available, RDS allocates a VPC to you by default.

    NOTICE:

    After the DB instance is created, the VPC cannot be changed.

    Subnet

    Improves network security by providing dedicated network resources that are logically isolated from other networks. Subnets take effect only within an AZ. The Dynamic Host Configuration Protocol (DHCP) function is enabled by default for subnets in which you plan to create RDS DB instances and cannot be disabled.

    Security Group

    Enhances security by controlling access to RDS from other services. You need to add inbound rules to a security group so that you can connect to your DB instance.

    If no security group is available, RDS allocates a security group to you by default.

    Table 5 Database configuration

    Parameter

    Description

    Administrator

    The default login name for the database is rdsuser.

    Administrator Password

    Must consist of 8 to 32 characters and contain at least three types of the following characters: uppercase letters, lowercase letters, digits, and special characters (~!@#$%^*-_+?,). Enter a strong password and periodically change it for security reasons.

    Keep this password secure. The system cannot retrieve it.

    After a DB instance is created, you can reset this password. For details, see section Resetting the Administrator Password.

    Confirm Password

    Must be the same as Administrator Password.

    Parameter Template

    Contains engine configuration values that can be applied to one or more DB instances. If you intend to create primary/standby DB instances, they use the same parameter template.

    NOTICE:

    If you use a custom parameter template when creating a DB instance, the specification-related parameter max server memory (MB) in the custom template is not delivered. Instead, the default value is used.

    You can modify the instance parameters as required after the DB instance is created. For details, see Modifying Parameters.

    Enterprise Project

    If the DB instance has been associated with an enterprise project, select the target project from the Enterprise Project drop-down list.

    You can also go to the ProjectMan console to create a project. For details about how to create a project, see the ProjectMan User Guide.

    Table 6 Batch creation

    Parameter

    Description

    Quantity

    RDS supports DB instance creation in batches. If you choose to create primary/standby DB instances and set Quantity to 1, a primary DB instance and a standby DB instance will be created synchronously.

    If you create multiple DB instances at a time, they will be named with four digits appended to the DB instance name. For example, if you enter instance, the first instance will be named instance-0001, the second instance-0002, and so on.

    The performance of your DB instance depends on its configurations. Hardware configuration items include the instance specifications, storage type, and storage space.

  6. Confirm the specifications.

    • If you need to modify your settings, click Previous.
    • If you do not need to modify your settings, click Submit.

  7. To view and manage the DB instance, go to the Instance Management page.

    • During the creation process, the DB instance status is Creating. When the creation process is complete, the instance status will change to Available.
    • The automated backup policy is enabled by default. An automated full backup is immediately triggered after a DB instance is created.
    • The default database port number is 1433. After a DB instance is created, you can change its port number.

      For details, see Changing a Database Port.