Service Overview Overview.pdfRelational Database Service Service Overview Issue 18 Date 2020-03-31 HUAWEI TECHNOLOGIES CO., LTD

Relational Database Service

Service Overview

Issue 18

Date 2020-03-31

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2020. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without priorwritten consent of Huawei Technologies Co., Ltd. Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.All other trademarks and trade names mentioned in this document are the property of their respectiveholders. NoticeThe purchased products, services and features are stipulated by the contract made between Huawei andthe customer. All or part of the products, services and features described in this document may not bewithin the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,information, and recommendations in this document are provided "AS IS" without warranties, guaranteesor representations of any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in thepreparation of this document to ensure accuracy of the contents, but all statements, information, andrecommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.Address: Huawei Industrial Base

Bantian, LonggangShenzhen 518129People's Republic of China

Website: https://e.huawei.com

Issue 18 (2020-03-31) Copyright © Huawei Technologies Co., Ltd. i

https://e.huawei.com

Contents

1 RDS..............................................................................................................................................1

2 Basic Concepts.......................................................................................................................... 3

3 Advantages............................................................................................................................... 63.1 Low Costs................................................................................................................................................................................... 63.2 High Performance................................................................................................................................................................... 73.3 High Security.............................................................................................................................................................................73.4 High Reliability......................................................................................................................................................................... 83.5 Comparison Between RDS and Self-Built Databases..................................................................................................9

4 Product Series.........................................................................................................................114.1 DB Instance Introduction....................................................................................................................................................114.2 Function Comparison...........................................................................................................................................................12

5 DB Instance Description.......................................................................................................155.1 DB Instance Types................................................................................................................................................................. 155.2 DB Instance Classes..............................................................................................................................................................165.3 DB Instance Storage Type.................................................................................................................................................. 205.4 DB Engines and Versions.................................................................................................................................................... 215.5 DB Instance Statuses........................................................................................................................................................... 22

6 Typical Applications..............................................................................................................266.1 Read/Write Splitting.............................................................................................................................................................266.2 Diversified Data Storage.....................................................................................................................................................26

7 Permissions Management................................................................................................... 28

8 Constraints.............................................................................................................................. 368.1 MySQL Constraints............................................................................................................................................................... 368.2 PostgreSQL Constraints.......................................................................................................................................................398.3 Microsoft SQL Server Constraints....................................................................................................................................40

9 Billing....................................................................................................................................... 42

10 Related Services...................................................................................................................44

11 RDS for MySQL Version Description............................................................................... 46

12 Function Differences of RDS for SQL Server DB Instances........................................51

Relational Database ServiceService Overview Contents

Issue 18 (2020-03-31) Copyright © Huawei Technologies Co., Ltd. ii

A Change History...................................................................................................................... 57

Relational Database ServiceService Overview Contents

Issue 18 (2020-03-31) Copyright © Huawei Technologies Co., Ltd. iii

1 RDS

HUAWEI CLOUD Relational Database Service (RDS) is a cloud-based web servicethat is reliable, scalable, easy to manage, and ready for immediate use. RDSsupports the following DB engines:

● MySQL● PostgreSQL● Microsoft SQL Server

HUAWEI CLOUD RDS provides a comprehensive performance monitoring system,multi-level security protection measures, and a professional databasemanagement platform, allowing you to easily set up and scale a relationaldatabase. On the RDS console, you can perform almost all necessary tasks and noprogramming is required. The console simplifies operation procedures and reducesroutine O&M workloads, so that you can focus on your application and servicedevelopment.

Using RDSYou can use RDS in either of the following ways:

● Management console: You can create and manage DB instances on themanagement console.

● API: You can invoke APIs to create and manage DB instances. For details, seethe Relational Database Service API Reference.

To help you better use RDS, see Basic Concepts and RDS

RDS for MySQLMySQL is one of the world's most popular open-source relational databases. Itworks with the Linux, Apache, and Perl/PHP/Python (LAMP) model to provideefficient web solutions. RDS for MySQL is reliable, secure, scalable, inexpensive,easy to manage, and immediately ready for use.

● It supports various web applications and is cost-effective, preferred by small-and medium-sized enterprises.

● A web-based console provides comprehensive monitoring information,making your operations easy and visual.

Relational Database ServiceService Overview 1 RDS

Issue 18 (2020-03-31) Copyright © Huawei Technologies Co., Ltd. 1

https://auth.huaweicloud.com/authui/login?#/login

https://support.huaweicloud.com/en-us/api-rds/rds_00_0001.html

● You can flexibly adjust the required resources based on your servicerequirements and pay for only what you use.

For details about the versions supported by RDS for MySQL, see section DBEngines and Versions.

RDS for PostgreSQLPostgreSQL is an open-source object-relational database management systemwith an emphasis on extensibility and standards compliance. It is known as themost advanced open-source database. RDS for PostgreSQL applies to business-oriented online transaction processing (OLTP) scenarios and supports NoSQL(JSON, XML, or hstore) and geographic information system (GIS) data types. It hasearned a reputation for reliability and data integrity, and applies to Internetwebsites, location-based applications, and complex data object processing.

● PostgreSQL supports the postgis plugin, which provides excellent spatialperformance at an international standard level. PostgreSQL offers functionssimilar to those of Oracle database systems, but is less expensive.

● PostgreSQL applies to various scenarios and is cost-effective. You can flexiblyscale resources based on your service requirements and pay for only what youuse.

For details about the versions supported by RDS for PostgreSQL, see section DBEngines and Versions.

RDS for SQL ServerMicrosoft SQL Server is a well-established commercial database with matureenterprise-class architecture. It supports one-stop deployment, ensuring key O&Mservices and lowering labor costs. With RDS for SQL Server, you can build a safeand stable database operation environment according to Huawei internationalsecurity standards. It is widely used in government, finance, medical care,education, and gaming. RDS for SQL Server is reliable, scalable, inexpensive, easyto manage, and immediately ready for use.

RDS for SQL Server provides the HA architecture, data security assurance, andbackup mechanism for fault recovery within seconds.

For details about the versions supported by RDS for SQL Server, see section DBEngines and Versions.

Relational Database ServiceService Overview 1 RDS


2 Basic Concepts

DB Instances

DB instances are the smallest management units used by RDS. Each is an isolateddatabase environment on the cloud. You can use RDS to create and manage DBinstances running various DB engines. For details about DB instance types,specifications, engines, versions, and statuses, see DB Instance Description.

DB Engines

RDS supports the following DB engines:

● MySQL

● PostgreSQL

● Microsoft SQL Server

For details about the supported versions, see DB Engines and Versions.

DB Instance Types

RDS DB instances are classified into three types: single, primary/standby, andprimary/standby (1/2). Different types of DB instances support different DBengines and instance specifications.

For details about the product series, see DB Instance Introduction and FunctionComparison.

DB Instance Classes

For details about supported DB engines and instance classes, including thenumber of vCPUs and memory (GB), see DB Instance Classes.

Automated Backups

When you create a DB instance, an automated backup policy is enabled bydefault. After the DB instance is created, you can modify the policy. RDS willautomatically create full backups for DB instances based on your settings.

Relational Database ServiceService Overview 2 Basic Concepts


Manual Backups

Manual backups are user-initiated full backups of DB instances. They are retaineduntil you delete them manually.

Finance Edition

The finance edition uses the three-node architecture with one master node andtwo slave nodes and ensures data consistency through the Paxos algorithm. It issuitable for core databases in the finance, securities, and insurance industries thathave high requirements on data security.

Figure 2-1 Finance edition structure

Regions and AZs

A region and availability zone (AZ) identify the location of a data center. You cancreate resources in a specific region and AZ.

● Regions are divided from the dimensions of geographical location andnetwork latency. Public services, such as Elastic Cloud Server (ECS), ElasticVolume Service (EVS), Object Storage Service (OBS), Virtual Private Cloud(VPC), Elastic IP (EIP), and Image Management Service (IMS), are sharedwithin the same region. Regions are classified as universal regions anddedicated regions. A universal region provides universal cloud services forcommon tenants. A dedicated region provides services of the same type onlyor for specific tenants.

● An AZ contains one or multiple physical data centers. Each AZ hasindependent cooling, fire extinguishing, moisture-proof, and electricityfacilities. Within an AZ, computing, network, storage, and other resources are



logically divided into multiple clusters. AZs within a region are interconnectedusing high-speed optical fibers to allow you to build cross-AZ high-availabilitysystems.

Figure 2-2 shows the relationship between regions and AZs.

Figure 2-2 Regions and AZs

HUAWEI CLOUD provides services in many regions around the world. You canselect a region and AZ as needed. For more information, see HUAWEI CLOUDGlobal Regions.

ProjectsProjects are used to group and isolate OpenStack resources (computing resources,storage resources, and network resources). A project can be a department or aproject team. Multiple projects can be created for one account.



https://www.huaweicloud.com/en-us/

https://www.huaweicloud.com/en-us/

3 Advantages

3.1 Low Costs

Instant AvailabilityYou can obtain a DB instance on the management console and access RDSthrough an ECS to reduce application response time and fees generated by publicnetwork traffic.

Elastic ScalingYou can flexibly adjust the required resources based on your service requirementsand pay for only what you use. Cloud Eye can monitor the changes of databasepressure and data storage space. You can adjust DB instance classes accordingly.

CompatibilityOperation methods of the database engines (DB engines) provided by RDS are thesame as those of the native engines. Additionally, RDS is also compatible withexisting programs and tools. With Data Replication Service (DRS), you can migratedata to RDS easily with low costs.

Easy O&MRoutine RDS maintenance and management operations, including hardware andsoftware fault handling and database patch updates, are easy to perform. Withthe management console, you can reboot DB instances, reset passwords, modifyparameters, view error or slow query logs, and restore data. Additionally, thesystem helps you monitor DB instances in real time and generates alarms if anerror occurs. You can check DB instance information at any time, including CPUusage, IOPS, database connections, and storage space usage.

Relational Database ServiceService Overview 3 Advantages


3.2 High Performance

Optimized PerformanceCombining its years of experience in database R&D, setup, and maintenance withthe cloud-based technology, HUAWEI CLOUD builds a database service that ishighly available, reliable, secure, scalable, instantly available, and easy to O&M.

Optimized HardwareRDS offers users stable and high-performance database services using servers thathave been developed and tested for many years by Huawei.

Optimized SQL SolutionsRDS can detect slowly-executed SQL statements. You can optimize the codesaccordingly.

High-end Hardware InvestmentAll servers used by RDS are evaluated by multiple parties, ensuring outstandingperformance and stability.

High-Speed AccessRDS can work with ECSs in the same region to communicate with each otherthrough the intranet. This shortens the response time of applications and reducesthe cost incurred by public network traffic.

Performance White Paper● RDS for MySQL Performance White Paper● RDS for PostgreSQL Performance White Paper● RDS for SQL Server Performance White Paper

3.3 High Security

Network IsolationRDS uses the Virtual Private Cloud (VPC) service and network security groups toisolate your DB instances. VPCs allow you to define IP addresses that are allowedto access RDS. You can run your DB instances in a VPC to improve security. Youcan configure subnets and security groups to control access to DB instances.

Access ControlRDS controls access through the account/IAM user and security groups. When youcreate an RDS DB instance, RDS will automatically create an account. You cancreate an IAM user as required and authorize database objects for the database



https://support.huaweicloud.com/en-us/pwp-rds/rds_swp_mysql_01.html

https://support.huaweicloud.com/en-us/pwp-rds/rds_03_0002.html

https://support.huaweicloud.com/en-us/pwp-rds/rds_02_0002.html

IAM user for the separation of permissions. VPC security groups have rules thatgovern both inbound and outbound traffic of DB instances.

Transmission Encryption

RDS uses Transport Layer Security (TLS) and Secure Sockets Layer (SSL) to offerencryption during transmission. You can download the Certificate Authority (CA)certificate from the RDS console and upload it when connecting to a database forauthentication.

Storage Encryption

RDS uses static encryption and tablespace encryption to encrypt the data to bestored. Encryption keys are managed by Key Management Service (KMS).

Data Deletion

When you delete an RDS DB instance, the disks it attaches, object storage spaceits backups occupy, and all data it stores will be deleted. The deleted data cannotbe viewed or restored.

Anti-DDoS

When you connect to an RDS DB instance through a public network, your DBinstance may be in a distributed denial-of-service attack. If the RDS securitysystem detects a DDoS attack, it will enable the anti-DDoS function. If thefunction cannot defend against the attack or the attack reaches the black holethreshold, black hole processing is triggered to ensure availability of the RDSservice.

Security Protection

RDS is protected by multiple layers of firewalls to defend against various maliciousattacks, such as DDoS attacks and SQL injections. You are advised to access RDSthrough a private network to protect RDS DB instances from DDoS attacks.

3.4 High Reliability

Dual-Host Hot Standby

RDS uses the hot standby architecture, in which failover upon fault occurrencetakes only some seconds.

Data Backup

RDS automatically backs up data every day and uploads backup files to ObjectStorage Service (OBS). The backup files can be stored for 732 days and can berestored with just a few clicks. You can set a custom backup policy and createmanual backups at any time.



Data RestorationYou can restore data from backups or to any point in time during the backupretention period. In most scenarios, you can use backup files to restore data to anexisting or a new DB instance at any time point within 732 days. After the data isverified, data can be migrated back to the primary RDS DB instance.

3.5 Comparison Between RDS and Self-Built Databases

PerformanceItem Cloud Database RDS Self-Built Database Service

Serviceavailability

For more information, seethe Elastic Cloud Server UserGuide.

Requires device procurement,primary/standby relationshipsetup, and RAID setup.

Datareliability

For more information, seethe Elastic Volume ServiceUser Guide.

Requires device procurement,primary/standby relationshipsetup, and RAID setup.

Systemsecurity

Defends against Anti-DDoSattacks and promptly repairsdatabase securityvulnerabilities.

Requires procurement ofexpensive devices and software,as well as manual detection andrepair of security vulnerabilities.

Databasebackup

Supports automatedbackups, manual backups,and custom backup retentionperiods.

Requires device procurement,setup, and maintenance.

Hardwareandsoftwareinvestment

Supports on-demand pricingand scaling without requiringhardware and softwareinvestment.

Requires large investment indatabase servers. The SQL Serverlicense must be paid forseparately.

Systemhosting

Not required. If a 2U server and primary/standby DB instances arerequired, you need to purchaseand set up two servers.

Maintenance cost

Not required. Requires large manpowerinvestment and professionaldatabase administrator (DBA) formaintenance.

Deploymentand scaling

Supports elastic scaling, fastupgrade, and on-demandenabling.

Requires procurement,deployment, and coordination ofhardware that matches originaldevices.



Item Cloud Database RDS Self-Built Database Service

Resourceutilization

Bills users based on theresources actually used,resulting in 100% resourceutilization.

Considers peak traffic, resultingin low resource utilization.



4 Product Series

4.1 DB Instance IntroductionCurrently, RDS DB instances are classified into the following types:● Single● Primary/Standby● Primary/Standby (1/2)

Different series support different DB engines and instance specifications.

Table 4-1 DB instance types

DB InstanceType

Description Scenarios

Single Uses the single-nodearchitecture. More cost-effectivethan the mainstream primary/standby DB instances.

● Personal learning● Microsites● Development and

testing environment ofsmall- and medium-sized enterprises

Primary/Standby Uses the HA architecture withone master node and one slavenode.

● Production databasesof large- and medium-sized enterprises

● Applications for theInternet, Internet ofThings (IoT), retail e-commerce sales,logistics, gaming, andother industries

Relational Database ServiceService Overview 4 Product Series


DB InstanceType

Description Scenarios

Primary/Standby(1/2)

Uses the three-node architecturewith one master node and twoslave nodes and ensures dataconsistency through the Paxosalgorithm. It is suitable for coredatabases that have highrequirements on data security.

● Finance industry● Securities industry● Insurance industry

4.2 Function ComparisonSingle DB instances use the single-node architecture. In contrast to themainstream primary/standby DB instances, a single DB instance contains only onenode and has no slave node for fault recovery. Primary/standby DB instances use athree-node architecture with one master node and two slave nodes to ensure dataconsistency.

Advantage Comparison● Single DB instances: support the creation of read replicas and error or slow

query log queries. Different from primary/standby DB instances that have twodatabase nodes, a single DB instance has only one node, reducing the price tohalf of primary/standby DB instances. As a result, restoration after a nodefailure on the primary/standby DB instances will take a long time. Therefore,primary/standby DB instances are not recommended for sensitive services thathave high requirements on database availability.

● Primary/Standby DB instances: The slave database node is used only forfailover and restoration. It does not provide services. The performance ofsingle DB instances is similar to or even higher than the primary/standby DBinstances.

● Primary/Standby (1/2): uses the three-node architecture with one masternode and two slave nodes and ensures data consistency through the Paxosalgorithm. It is suitable for core databases in the finance, securities, andinsurance industries that have high requirements on data security.

Table 4-2 Function comparisons

DB Engine Single Primary/Standby Primary/Standby(1/2)

MySQL 8.05.75.6

8.05.75.6

5.7




PostgreSQL Enhanced Edition12, which isavailable only forusers with the openbeta test (OBT)permission. You cancontact customerservice to apply forthe permission.11109.69.5

Enhanced Edition12, which isavailable only forusers with the OBTpermission. You cancontact customerservice to apply forthe permission.11109.69.5

Not supported fornow

MicrosoftSQL Server

2017 StandardEdition2017 Web Edition2016 EnterpriseEdition2016 StandardEdition2016 Web Edition2014 StandardEdition2014 Web Edition2014 EnterpriseEdition2012 StandardEdition2012 Web Edition2012 EnterpriseEdition2008 R2 WebEdition

2017 EnterpriseEdition2017 StandardEdition2016 EnterpriseEdition2016 StandardEdition2014 EnterpriseEdition2014 StandardEdition2012 EnterpriseEdition2012 StandardEdition2008 R2 EnterpriseEdition

Not supported fornow

Number ofnodes

1 2 3

Specifications

vCPUs: a maximumof 60Memory: amaximum of 512 GBStorage space: amaximum of 4 TB

vCPUs: a maximumof 60Memory: amaximum of 512 GBStorage space: amaximum of 4 TB

vCPUs: a maximumof 60Memory: amaximum of 512GBStorage space: amaximum of 4 TB




Monitoringand alarms

Supported Supported Supported

Securitygroup


Backupsandrestorations


Parametersettings


SSL Supported Supported Supported

Logmanagement


Readreplicas(need to becreated)


High-frequencymonitoring


Primary/standbyswitchoveror failover

Not supported Supported Supported

Standby DBinstancemigration

Not supported Supported Supported

Manualprimary/standbyswitchover

Supported Supported Not supported

Instanceclasschange

Supported Supported Not supported



5 DB Instance Description

5.1 DB Instance TypesDB instances are the smallest management units used by RDS. Each is an isolateddatabase environment on the cloud. A DB instance can contain multiple user-created databases, and you can access it by using the same tools and applicationsthat you use with a stand-alone DB instance. You can create and modify DBinstances using the management console or APIs. RDS does not have limits on thenumber of running DB instances. Each DB instance has a DB instance identifier.

DB instances are classified into the following types.

Table 5-1 DB instance types

DB Instance Type Description

Single Uses a single-node architecture. More cost-effective than primary/standby DB instances.

Primary/Standby Uses an HA architecture with one master node andone slave node.

Read replica Uses a single-node architecture (without a standbynode).

Primary/Standby (1/2) Uses a three-node architecture with one masternode and two slave nodes and ensures dataconsistency through the Paxos algorithm. Suitablefor core databases that have high requirements ondata security.

Only Microsoft SQL Server 2017 Enterprise Edition supports read replicas. Othereditions of Microsoft SQL Server do not support read replicas.

You can use RDS to create and manage DB instances running various DB engines.

Relational Database ServiceService Overview 5 DB Instance Description


For details about differences and function comparison between different instancetypes, see DB Instance Introduction and Function Comparison.

5.2 DB Instance Classes

Table 5-2 DB instance classes

Instance Class vCPUs Memory(GB)

Supported DB Engine

General-enhanced 1 2 ● MySQL● PostgreSQL

1 4 ● MySQL● PostgreSQL

1 8 MySQL

2 4 ● MySQL● PostgreSQL● Microsoft SQL Server

(only supported forWeb Editions of 2017,2016, 2014, 2012, and2008 R2, 2008 R2Enterprise Edition, andStandard Editions of2012, 2014, and 2016)


(only supported forEnterprise Editions of2017, 2016, 2014,2012, and 2008 R2,and Standard Editionsof 2017, 2016, 2014,and 2012)


(only supported forEnterprise Editions of2017, 2016, 2014,2012, and 2008 R2,and Standard Editionsof 2017, 2016, 2014,and 2012)




Supported DB Engine




8 16 ● MySQL● Microsoft SQL Server






(only supported forStandard Editions of2017, 2016, 2014, and2012, and EnterpriseEditions of 2016, 2014,2008 R2, and 2012)

32 64 MySQL


(only supported forEnterprise Editions of2017, 2016, 2014, and2012)




Supported DB Engine

32 256 Microsoft SQL Server(only supported forEnterprise Editions of2017, 2016, 2014, 2008R2, and 2012)



(only supported forEnterprise Editions of2017, 2016, 2014, and2012)


(only supported forEnterprise Editions of2017, 2016, 2014, 2008R2, and 2012)

General-enhanced II 2 4 MySQL

2 8 MySQL

2 16 MySQL

4 8 MySQL

4 16 MySQL

4 32 MySQL

8 16 MySQL

8 32 MySQL

8 64 MySQL

16 32 MySQL

16 64 MySQL

16 128 MySQL

32 64 MySQL

32 128 MySQL

64 128 MySQL




Supported DB Engine

64 256 MySQL

64 512 MySQL

Kunpeng general-enhancedNOTE

Kunpeng general-enhanced DB instancesare available only forusers with the OBTpermission. You cancontact customer serviceto apply for thepermission.



















Supported DB Engine



Ultra-high performance(advanced)NOTE

1. The ultra-highperformance(advanced) isavailable only forusers with therequired permission.You can contactcustomer service toapply for thepermission.

2. This DB instance classonly supports thecreation of primary/standby DB instancesand read replicas.Single DB instancesand primary/standby(1/2) DB instances arenot supported.

4 32 MySQL

8 64 MySQL

16 128 MySQL

32 256 MySQL

The DB instance specifications vary according to site requirements.

5.3 DB Instance Storage TypeThe database system is generally an important system in the IT system and hashigh requirements on storage I/O performance. You can select a desired storagetype as required. You cannot change the storage type after the DB instance iscreated.

Table 5-3 Storage type

Storage Type Description

Ultra-high I/O The maximum throughput is 350 MB/s.



Storage Type Description

Ultra-high I/O(advanced)

Considers both the local disk write speed and cloud disk datareliability. MySQL logs are written to local disks to improvedata write speed. Data is written to cloud disks to improvedata reliability.NOTE

The ultra-high I/O (advanced) storage type supports only ultra-highperformance (advanced) DB instances.

5.4 DB Engines and VersionsTable 5-4 lists the DB engines and versions supported by RDS.

For new applications, you are advised to use the latest major version of the DBengine, for example, MySQL 5.7. When you create a DB instance, you can select amajor DB engine version only (such as MySQL 5.7). The system will automaticallyselect an appropriate minor version (such as 5.7.23). After the DB instance iscreated, you can view the minor version in the DB Engine Version column on theInstance Management page. The DB engine and version vary according to siterequirements.

Figure 5-1 DB engine version

Table 5-4 DB engines and versions

DB Engine Version

MySQL ● 8.0● 5.7● 5.6

PostgreSQL ● Enhanced Edition. For more information, seeIntroduction to PostgreSQL Enhanced Edition.

● 12, which is available only for users with the OBTpermission. You can contact customer service toapply for the permission.

● 11● 10● 9.6● 9.5



https://support.huaweicloud.com/en-us/usermanual-rds/rds_03_0018.html

DB Engine Version

Microsoft SQL Server ● 2017 Enterprise Edition● 2017 Standard Edition● 2017 Web Edition, which supports single DB

instances only.● 2016 Enterprise Edition● 2016 Standard Edition● 2016 Web Edition, which supports single DB



instances only.● 2008 R2 Enterprise Edition, which supports primary/

standby DB instances only.● 2008 R2 Web Edition, which supports single DB

instances only.

5.5 DB Instance Statuses

DB Instance StatusesThe status of a DB instance indicates the health of the DB instance. You can usethe management console or API to view the status of a DB instance.

Table 5-5 DB instance statuses

Status Description

Available DB instance is available.

Abnormal DB instance is abnormal.

Creating DB instance or backup is being created.

Creation failed DB instance has failed to be created.

Switchover inprogress

Standby DB instance is being switched over to the primary DBinstance.



Status Description

Changing typeto primary/standby

Single DB instance is being changed to primary/standby DBinstances.

Rebooting DB instance is rebooting because of a user request or amodification that requires a reboot for the changes to takeeffect.

Changing port DB instance port is being changed.

Changinginstance class

CPU or memory of a DB instance is being modified.

Scaling up Storage space of a DB instance is being scaled up.

Restoring DB instance is being restored from a backup.

Restore failed DB instance fails to be restored.

Frozen DB instance is frozen when the account balance is less thanor equal to ¥0. Retained frozen DB instances are unfrozenonly after your account is recharged and the overduepayments are cleared. For details, see Account Freezing andUnfreezing.

Storage full Storage space of the DB instance is full. Data cannot bewritten to databases.

Changing toyearly/monthly

Pay-per-use DB instance is being changed to a yearly/monthly DB instance.

Deleted DB instance has been deleted and will not be displayed in theinstance list.

Upgradingminor version

DB instance minor version is being upgraded.

Upgrading DB engine version is being upgraded.

Migratingstandby DBinstance

MySQL standby DB instance is being migrated to an AZ in thesame region.

Parameter Template Statuses

You can use the management console or API to view the status of a parametertemplate after parameters are modified.

Table 5-6 Parameter template statuses

Status Description

In-sync A database parameter has taken effect.



Status Description

Applying A modification to a database parameter is being applied.

Pending reboot A modification to a database parameter is waiting for a DBinstance to reboot before it can take effect.

Account Freezing and UnfreezingAfter a settlement:

● If your account balance is greater than or equal to ¥0, your operations are notrestricted.

● If your account balance is less than ¥0, RDS will freeze your DB instances andremind you of charging the account. In this case, you cannot performoperations related to adding resources. If the account is not recharged withinthe DB instance retention period, the frozen DB instances will be deleted.Retained frozen DB instances are unfrozen only after your account isrecharged and the overdue payments are cleared. Related services arerestored after the unfreezing. For details about the DB instance retentionperiod, see the following table.

Table 5-7 DB instance retention period

Billing Type Yearly/Monthly Pay-per-Use

CustomerLevel

Grace Period(Days)

RetentionPeriod(Days)

Grace Period(Days)

RetentionPeriod(Days)

V5 7 15 1 15

V4

V3 7 7 1 7

V2 1 7 0 7

V1

V0 1 1 0 1



● Operations related to adding resources include creating DB instances, expanding diskcapacity, changing instance classes, adding read replicas, migrating data, setting ormodifying automated backup policies, and creating or replicating backups.

● For yearly/monthly DB instances, if you delete them before the expiration date, allrelated resources will be released and RDS will not trigger the refund processautomatically. You need to contact customer service and apply for a refund followingthe unsubscription procedure.

● If a DB instance is frozen, its status is unknown. After it is unfrozen, its status may befaulty and is unavailable for a short period of time before the system restorationoperation is complete.



6 Typical Applications

6.1 Read/Write SplittingMySQL, PostgreSQL, and SQL Server 2017 Enterprise Edition DB instances supportread replicas to offload read traffic from primary DB instances.

Both primary DB instances and read replicas of RDS MySQL and PostgreSQLdatabases have independent connection addresses. A maximum of five readreplicas can be created for each primary MySQL or PostgreSQL DB instance. Fordetails about how to create a read replica, see Creating a Read Replica.

To improve the system processing capability, you can simply create read replicaswithout the need of changing your existing applications.

Figure 6-1 Read/Write splitting

6.2 Diversified Data StorageRDS supports diverse storage extension through Distributed Cache Service (DCS)for Memcached, DCS for Redis, and OBS.

Relational Database ServiceService Overview 6 Typical Applications


https://support.huaweicloud.com/en-us/usermanual-rds/en-us_topic_add_read_replica.html

Figure 6-2 Diversified data storage

Relational Database ServiceService Overview 6 Typical Applications


7 Permissions Management

If you need to assign different permissions to employees in your enterprise toaccess your RDS resources, IAM is a good choice for fine-grained permissionsmanagement. IAM provides identity authentication, permissions management,and access control, helping you secure access to your HUAWEI CLOUD resources.

With IAM, you can use your HUAWEI CLOUD account to create IAM users for youremployees, and assign permissions to the users to control their access to specificresource types. For example, some software developers in your enterprise need touse RDS resources but must not delete them or perform any high-risk operations.To achieve this result, you can create IAM users for the software developers andgrant them only the permissions required for using RDS resources.

If your HUAWEI CLOUD account does not need individual IAM users forpermissions management, you may skip over this chapter.

IAM can be used free of charge. You pay only for the resources in your account.For more information about IAM, see the IAM Service Overview.

RDS PermissionBy default, new IAM users do not have permissions assigned. You need to add auser to one or more groups, and attach permissions policies or roles to thesegroups. Users inherit permissions from the groups to which they are added andcan perform specified operations on cloud services based on the permissions.

RDS is a project-level service deployed and accessed in specific physical regions. Toassign RDS permissions to a user group, specify the scope as region-specificprojects and select projects for the permissions to take effect. If All projects isselected, the permissions will take effect for the user group in all region-specificprojects. When accessing RDS, users need to switch to a region where they havebeen authorized to use RDS.

You can grant users permissions by using roles and policies.● Roles: A type of coarse-grained authorization mechanism that defines

permissions related to user responsibilities. This mechanism provides only alimited number of service-level roles for authorization. When using roles togrant permissions, you need to also assign other roles on which thepermissions depend to take effect. However, roles are not an ideal choice forfine-grained authorization and secure access control.

Relational Database ServiceService Overview 7 Permissions Management


https://support.huaweicloud.com/en-us/productdesc-iam/iam_01_0026.html

● Policies: A type of fine-grained authorization mechanism that definespermissions required to perform operations on specific cloud resources undercertain conditions. This mechanism allows for more flexible policy-basedauthorization, meeting requirements for secure access control. For example,you can grant IAM users only the permissions for managing a certain type ofRDS resources. Most policies define permissions based on APIs. For the APIactions supported by RDS, see Permissions Policies and Supported Actions.

Table 7-1 lists all the system-defined roles and policies supported by RDS.

Table 7-1 System policy summary

Policy Name/System Role

Description Category Dependencies

RDS FullAccess All permissions System policy N/A

RDSReadOnlyAccess

Read-only permissions forRDS

System policy N/A

RDSAdministrator

Administrator permissionsfor RDS

System role The TenantGuest andServerAdministratorroles need tobe assigned inthe sameproject.

Table 7-2 lists the common operations supported by each system policy of RDS.Please choose proper system policies according to this table.

Table 7-2 Common operations supported by the RDS system policies

Operation RDS FullAccess RDSReadOnlyAccess

RDSAdministrator

Creating anRDS DBinstance

√ x √

Deleting anRDS DBinstance

√ x √

Querying anRDS DBinstance list

√ √ √




Table 7-3 Common operations and supported actions

Operation Actions Remarks

Creating a DBinstance

rds:instance:createrds:param:list

To select a VPC,subnet, and securitygroup, configure thefollowing actions:vpc:vpcs:listvpc:vpcs:getvpc:subnets:getvpc:securityGroups:getTo create anencryption DBinstance, you need toconfigure the KMSAdministratorpermission in theproject.

Changing DBinstancespecifications

rds:instance:modifySpec N/A

Scaling up storagespace

rds:instance:extendSpace N/A

Changing a DBinstance type fromsingle to primary/standby

rds:instance:singleToHa If the original singleDB instance isencrypted, you need toconfigure the KMSAdministratorpermission in theproject.

Rebooting a DBinstance

rds:instance:restart N/A

Deleting a DBinstance

rds:instance:delete N/A

Querying detailsabout DB instances

rds:instance:list N/A

Viewing DB instancedetails

rds:instance:list If the VPC, subnet, andsecurity group aredisplayed in the DBinstance list, you needto configure vpc:*:getand vpc:*:list.

Changing a DBinstance password

rds:password:update N/A




Changing a port rds:instance:modifyPort N/A

Changing a floatingIP address

rds:instance:modifyIp To query the list ofunused IP addresses,configure the followingactions:vpc:subnets:getvpc:ports:get

Changing a DBinstance name

rds:instance:modify N/A

Changing themaintenancewindow

rds:instance:modify N/A

Performing a manualswitchover

rds:instance:switchover N/A

Changing thesynchronize model

rds:instance:modifySynchroni-zeModel

N/A

Changing thefailover priority

rds:instance:modifyStrategy N/A

Changing a securitygroup

rds:instance:modifySecurityGroup

N/A

Binding or unbindingan EIP

rds:instance:modifyPublicAccess

To query public IPaddresses, configurethe following actions:vpc:publicIps:getvpc:publicIps:list

Modifying therecycling policy

rds:instance:setRecycleBin N/A

Querying therecycling policy


Enabling or disablingSSL

rds:instance:modifySSL N/A

Enabling or disablingevent scheduler

rds:instance:modifyEvent N/A

Configuring read/write splitting

rds:instance:modifyProxy N/A

Applying for aprivate domainname

rds:instance:createDns N/A




Migrating a standbyDB instance toanother AZ

rds:instance:create Standby DB instancemigration involvesoperations on the IPaddress in the subnet.For encrypted DBinstances, you need toconfigure the KMSAdministratorpermission in theproject.

Restoring tables to aspecified point intime

rds:instance:tableRestore N/A

Configuring TDEpermission

rds:instance:tde Only used forMicrosoft SQL ServerDB instances.

Changing hostpermission

rds:instance:modifyHost N/A

Querying hosts ofthe correspondingdatabase account


Obtaining aparameter templatelist

rds:param:list N/A

Creating a parametertemplate

rds:param:create N/A

Modifyingparameters in aparameter template

rds:param:modify N/A

Applying aparameter template

rds:param:apply N/A

Modifyingparameters of aspecified DB instance

rds:param:modify N/A

Obtaining theparameter templateof a specified DBinstance

rds:param:list N/A

Obtainingparameters of aspecified parametertemplate

rds:param:list N/A




Deleting a parametertemplate

rds:param:delete N/A

Resetting aparameter template

rds:param:reset N/A

Comparingparameter templates

rds:param:list N/A

Saving parameters ina parametertemplate

rds:param:save N/A

Querying aparameter templatetype

rds:param:list N/A

Setting anautomated backuppolicy

rds:instance:modifyBackupPoli-cy

N/A

Querying anautomated backuppolicy


Creating a manualbackup

rds:backup:create N/A

Obtaining a backuplist

rds:backup:list N/A

Obtaining the linkfor downloading abackup file

rds:backup:download N/A

Deleting a manualbackup

rds:backup:delete N/A

Replicating a backup rds:backup:create N/A

Querying therestoration timerange


Restoring data to anew DB instance

rds:instance:create To select a VPC,subnet, and securitygroup, configure thefollowing actions:vpc:vpcs:listvpc:vpcs:getvpc:subnets:getvpc:securityGroups:get




Restoring data to anexisting or originalDB instance

rds:instance:restoreInPlace N/A

Obtaining the binlogclearing policy

rds:binlog:get N/A

Merging binlog files rds:binlog:merge N/A

Downloading abinlog file

rds:binlog:download N/A

Deleting a binlog file rds:binlog:delete N/A

Configuring a binlogclearing policy

rds:binlog:setPolicy N/A

Obtaining adatabase backup filelist

rds:backup:list N/A

Obtaining a backupdatabase list at aspecified time point

rds:backup:list N/A

Querying a databaseerror log

rds:log:list N/A

Querying a databaseslow log

rds:log:list N/A

Downloading adatabase error log

rds:log:download N/A

Downloading adatabase slow log

rds:log:download N/A

Enabling or disablingthe audit logfunction

rds:auditlog:operate N/A

Obtaining an auditlog list

rds:auditlog:list N/A

Querying the auditlog policy

rds:auditlog:list N/A

Obtaining the linkfor downloading anaudit log

rds:auditlog:download N/A

Obtaining aswitchover log

rds:log:list N/A

Creating a database rds:database:create N/A




Querying detailsabout databases

rds:database:list N/A

Querying authorizeddatabases of aspecified user

rds:database:list N/A

Dropping a database rds:database:drop N/A

Creating a databaseaccount

rds:databaseUser:create N/A

Querying detailsabout databaseaccounts

rds:databaseUser:list N/A

Querying authorizedaccounts of aspecified database

rds:databaseUser:list N/A

Deleting a databaseaccount

rds:databaseUser:drop N/A

Authorizing adatabase account

rds:databasePrivilege:grant N/A

Revokingpermissions of adatabase account

rds:databasePrivilege:revoke N/A

Viewing a taskcenter list

rds:task:list N/A

Deleting a task fromthe task center

rds:task:delete N/A

Submitting an orderfor a yearly/monthlyDB instance

bss:order:update N/A

Managing a tag rds:instance:modify N/A

Helpful Links● IAM Service Overview● Creating a User Group and User and Granting RDS Permissions● Permissions Policies and Supported Actions



https://support.huaweicloud.com/en-us/productdesc-iam/iam_01_0026.html



8 Constraints

8.1 MySQL ConstraintsTable 8-1 shows the constraints designed to ensure the stability and security ofRDS for MySQL.

Table 8-1 Function constraints

Function Item Constraints

Database access ● If DB instances are not bound with EIPs, theinstances must be in the same VPC subnet as theECS.

● RDS read replicas must be created in the samesubnet as the primary DB instance.

● The ECS must be allowed by the security group toaccess RDS DB instances.By default, RDS cannot be accessed through an ECSin a different security group. You need to add aninbound rule to the RDS security group.

● The default RDS port is 3306. You can change it ifyou want to access RDS through another port.

Deployment ECSs in which DB instances are deployed are not visibleto you. You can access the DB instances only throughan IP address and a port number.

Database rootpermissions

Only the root user permissions are provided on theinstance creation page. For more information aboutroot permissions, see Table 8-2.

Database parametermodification

Most parameters can be modified on the RDS console.

Relational Database ServiceService Overview 8 Constraints



Data import ● Command-line interface (CLI) or graphical userinterface (GUI)

● DRS● MySQL CLI toolFor details, see Migrating MySQL Data Using DRS.

MySQL storage engine For details, see What Storage Engines Does the RDSfor MySQL Support?

Database replicationsetup

RDS for MySQL provides a dual-node cluster with theprimary/standby replication architecture. You do notneed to set up replication. The standby DB instance isnot visible to users and therefore you cannot access itdirectly.

DB instance reboot DB instances cannot be rebooted through commands.They must be rebooted on the RDS console.

RDS backup files RDS backup files are stored in OBS buckets and are notvisible to you.

Table 8-2 Root user permissions

Permission Level Description Supported

Select Table Query permissions Supported

Insert Table Insert permissions

Update Table Update permissions

Delete Table Delete permissions

Create Database,table, orindex

Permissions of creatingdatabases, tables, or indexes

Drop Databaseor table

Permissions of deletingdatabases or tables

Reload Servermanagement

Permissions of running thefollowing commands: flush-hosts, flush-logs, flush-privileges, flush-status, flush-tables, flush-threads, refresh,and reload

Process Servermanagement

Permissions of viewingprocesses



https://support.huaweicloud.com/en-us/usermanual-rds/rds_migration_mysqlbydrs.html

https://support.huaweicloud.com/en-us/rds_faq/rds_faq_0041.html

https://support.huaweicloud.com/en-us/rds_faq/rds_faq_0041.html


Grant Database,table, orstoredprogram

Permissions of granting accesscontrol

References Databaseor table

Foreign key operationpermissions

Index Table Index permissions

Alter Table Permissions of altering tables,such as adding fields or indexes

Show_db Servermanagement

Permissions of viewingdatabase connections

Create_tmp_table Servermanagement

Permissions of creatingtemporary tables

Lock_tables Servermanagement

Permissions of locking tables

Execute Storedprocedure

Permissions of executingstorage procedures

Repl_slave Servermanagement

Replication permissions

Repl_client Servermanagement

Replication permissions

Create_view View Permissions of creating views

Show_view View Permissions of viewing views

Create_routine Storedprocedure

Permissions of creating storageprocedures

Alter_routine Storedprocedure

Permissions of altering storageprocedures

Create_user Servermanagement

Permissions of creating users

Event Database Event triggers

Trigger Database Triggers




Super Servermanagement

Permissions of killing threads Notsupported

File File on theserver

Permissions of accessing fileson database server nodes

Shutdown Servermanagement

Permissions of shutting downdatabases

Create_tablespace Servermanagement

Permissions of creatingtablespaces

8.2 PostgreSQL ConstraintsTable 8-3 shows the constraints designed to ensure the stability and security ofRDS for PostgreSQL.



Database access ● If remote access is not enabled, RDS DBinstances must be in the same VPC subnet as theECS.

● RDS read replicas must be created in the samesubnet as the primary DB instance.

● The ECS must be allowed by the security groupto access RDS DB instances.By default, RDS cannot be accessed through anECS in a different security group. You need toadd an inbound rule to the RDS security group.

● The default RDS port is 5432. You can change itif you want to access RDS through another port.

Deployment ECSs in which DB instances are deployed are notvisible to you. You can access the DB instances onlythrough an IP address and a port number.

Database rootpermissions

Only the root user permissions are provided on theinstance creation page.NOTE

The root user has the following permissions: Create role,Create DB, and Replication.

Database parametermodification

Most parameters can be modified on the RDSconsole.




Data import ● Use the DRS service.● You can use the psql command line tool to

migrate data.

For details, see Migrating PostgreSQL Data UsingDRS.

Database replicationsetup

RDS for PostgreSQL provides a dual-node clusterwith the primary/standby replication architecture.You do not need to set up replication. The standbyDB instance is not visible to users and therefore youcannot access it directly.

DB instance reboot DB instances cannot be rebooted throughcommands. They must be rebooted on the RDSconsole.

RDS backup files RDS backup files are stored in OBS buckets and arenot visible to users.

8.3 Microsoft SQL Server ConstraintsRDS for SQL Server only supports DB instances under the License Included modeland does not support "bring your own license" (BYOL). After a DB instance iscreated, it contains the Microsoft SQL Server software license.

Table 8-4 shows the constraints designed to ensure the stability and security ofRDS for SQL Server.

Microsoft SQL Server DB instances are classified into two types: single andprimary/standby. DB instances of different series have different functionconstraints. For details, see DB Instance Introduction.


Function Item Primary/Standby Single

Maximum number ofdatabases

100 (can be increased) 100 (can be increased)

Number of databaseaccounts

Unlimited Unlimited

Creation of user, LOGIN, ordatabase

Supported Supported

Database-level DDL trigger Supported Supported

Database permissionauthorization

Supported Supported





https://support.huaweicloud.com/en-us/productdesc-rds/rds_01_0010.html#


KILL permission Supported Supported

LinkServer Supported Supported

Distributed transaction Supported Supported

SQL Profiler Supported Supported

Tuning Adviser Supported Supported

Change Data Capture (CDC) Supported Supported

Change tracking Supported Supported

Windows domain accountlogin

Supported Supported

Email Supported Supported

SQL Server IntegrationServices (SSIS)

Not supported Not supported

SQL Server Analysis Services(SSAS)


SQL Server ReportingServices (SSRS)

Supported Supported

R Services Not supported Not supported

Common LanguageRuntime (CLR)

Support for SAFE mode Support for SAFEmode

Asynchronouscommunication


Replication subscription Not supported Not supported

Policy management Not supported Not supported



9 Billing

HUAWEI CLOUD RDS allows you to pay only for what you use. There is nominimum fee.

Billing Items

HUAWEI CLOUD RDS charges you for your DB instances, database storage, andbackup storage (optional).

Table 9-1 RDS billing

Billing Item Description

DB instance ● RDS charges for the specifications of your DB instances.(DB instances are classified as three types: primary DBinstances, primary/standby DB instances, and readreplicas).

● DB instances can be billed on a yearly/monthly basis orpay-per-use (hourly) basis.

Databasestorage

● RDS charges for your database storage.● DB instances can be billed on a yearly/monthly basis or

pay-per-use (hourly) basis.

Backup storage(optional)

RDS provides free backup storage space of almost the samesize as your purchased storage space. Tiered pricing initiatesafter the RDS backup storage usage exceeds 100% of yourpurchased database storage space.

Public networktraffic

RDS DB instances are publicly accessible and you are chargedfor the generated public network traffic. Private networktraffic is free of charge.

For pricing details, see Product Pricing Details. You can use the RDS pricecalculator to quickly calculate an estimate price of a DB instance with your desiredspecifications.

Relational Database ServiceService Overview 9 Billing


https://www.huaweicloud.com/en-us/pricing.html?tab=detail#/rds

Billing Modes

RDS provides two billing modes: pay-per-use and yearly/monthly. Pay-per-use isrecommended if you are unsure of your future service needs and want to avoidpaying for unused resources. However, if you are sure of your needs, yearly/monthly will be less expensive.

● Yearly/Monthly: This billing mode offers a larger discount than pay-per-useand is recommended for uses who can predict long-term resource usage.

● Pay-per-use (hourly): This billing mode is flexible, enabling you to start andstop services anytime. You pay only for what you use. The minimum time unitis one hour. Less than an hour is regarded as an hour.

● You can change the billing mode from pay-per-use to yearly/monthly or fromyearly/monthly to pay-per-use.

Changing Configurations● Modifying RDS DB instance specifications: You can modify RDS DB instance

specifications based on service requirements. After the modification, you arecharged based on the new instance specifications.

● Scaling up storage space: You can scale up storage space based on servicerequirements. After scaling the storage space, you are charged based on thenew storage space. Storage space can only be scaled up, not down. Theminimum increment for each scaling is 10 GB.

Renewal

Currently, RDS supports the yearly/monthly and pay-per-use billing modes. The DBinstance specifications depend on your processing power and memoryrequirements.

● Pay-per-use: You are charged based on the actual usage by hour. Partial hoursare billed as full hours. You can use the service as long as your accountbalance is sufficient. If your account balance is insufficient, it will be inarrears. Top up your account in a timely manner.

● Yearly/monthly: An upfront payment is required when you purchase theservice. No additional fees are incurred during your usage.

To renew the subscription, go to the Renewals page.

Expiration and Overdue Payment● Service Expiration

If your purchased DB instance has expired, see Stopping Services andReleasing Resources in the Billing Center User Guide.

● Overdue Payment

If your purchased DB instance is in arrears, see Repaying Arrears in theBilling Center User Guide.

Relational Database ServiceService Overview 9 Billing


https://account.huaweicloud.com/usercenter/#/userindex/renewalManagement

https://support.huaweicloud.com/en-us/usermanual-billing/en-us_topic_0083039587.html



10 Related Services

The following figure shows the relationship between RDS and other services.

Figure 10-1 Relationship between RDS and other services

Table 10-1 Related services

Service Name Description

Elastic CloudService (ECS)

Enables you to access RDS DB instances through an ECS toreduce application response time and public network trafficfees.

Relational Database ServiceService Overview 10 Related Services


Service Name Description

Virtual PrivateCloud (VPC)

Isolates your networks and controls access to your RDS DBinstances.

Object StorageService (OBS)

Stores automated and manual backups of your RDS DBinstances.

Cloud Eye Acts as an open monitoring platform that monitors RDSresources in real time. It reports alarms and issues warningspromptly to ensure that services are running properly.

Cloud TraceService (CTS)

Provides records of operations on cloud service resources,enabling you to query, audit, and backtrack operations.

Database SecurityService (DBSS)

Prevents database attacks, ensuring database security onthe cloud.

Distributed CacheService (DCS)

Caches hot data to accelerate access to databases,improving user experience.

DistributedDatabaseMiddleware(DDM)

Connects to multiple RDS MySQL DB instances and allowsyou to access distributed databases.

Data ReplicationService (DRS)

Smoothly migrates databases to the cloud.

Data AdminService (DAS)

Provides a visualized GUI interface for you to connect andmanage cloud databases.

Relational Database ServiceService Overview 10 Related Services


11 RDS for MySQL Version Description

MySQL 8.020191215

New features

● Upgrade the minor version to 8.0.17.● Support parallel index builds.

20191015

Fixed bugs.

The replication delay is abnormal when SQL_MODE is set toPAD_CHAR_TO_FULL_LENGTH.

20190915

New features

● Support thread pools.● Upgrade OpenSSL to 1.1.1a.● Support the Common Type System (CTS) syntax: create table xx select.● Support show full processlist queries for memory usage and CPU usage of

user threads.

MySQL 5.720191215

New features

● DDL operation progress: Obtain the progress of adding columns or indexesthrough information_schema.innodb_alter_table_progress.

● Long transactions: Obtain the transaction execution time Trx_Executed_Timethrough SHOW PROCESSLIST.

● Online extension of the String field length: Extend the VARCHAR field lengthfrom COPY to INPLACE.

20191015

Relational Database ServiceService Overview 11 RDS for MySQL Version Description


New features

● Upgrade the minor version to 5.7.27.● Instant add column: Columns are quickly added to a table without copying

data and without occupying disk space and disk I/Os. Data can be updated inreal time during peak hours.

● Logical read-ahead: During a full table scan query or range scan query, logicalread-ahead accelerates the execution speed and reduces disk I/Os.

● MDL lock view: Obtain the lock information of the MDL held or waiting bythe thread through information_schema.metadata_lock_info.

● SQL filtering: Set SQL statements to filter out the SQL statements that are notprocessed. This function ensures the stability of core services during peakhours.

20190815

New features

Jemalloc memory management: Replace the jlibc memory management moduleto reduce the memory usage and improve memory allocation efficiency.

20190615

New features

● Upgrade the minor version to 5.7.25.● Support implicit primary keys: If a user does not specify a primary key or

unique index when creating a table, the system automatically creates animplicit primary key to resolve the primary/standby replication delay causedby no primary keys.

20190515

● New featuresWhen sync_binlog and innodb_flush_log_at_trx_commit are set to valuesother than 1, the crash safe data security of the standby database isguaranteed. In sysbench high-concurrent pure write request scenarios, thereplication delay between primary and standby DB instances is almost zero.

● Fixed bugs– When relay_log_recovery is set to ON, the standby database cannot be

rebooted after being killed in certain scenarios.– When SQL_MODE is set to PAD_CHAR_TO_FULL_LENGTH, data

replication between primary and standby DB instances is abnormal.– Errors occur on performance_schema statistics repeatedly.– When ORDER BY queries are performed on tables about information

replication in Performance_schema, the return value is empty.

20190115

Fixed bugs

● After the flush operation is performed on read replicas, data replication isinterrupted and data is inconsistent between primary and standby DBinstances.



● The replication thread of the standby database is deadlocked due to theREPAIR or OPTIMIZE statements.

20181115

New features

● Upgrade the minor version to 5.7.23.● Support creation and deletion of temporary tables in transactions when GTID

is enabled.● Support table-level multi-threaded slaves (MTS) parallel playback.

20180715

New features

● Upgrade the minor version to 5.7.22.● Support thread pools.● Support the CTS syntax: create table xx select.● Operator pushdown: The aggregation operator is pushed down to the storage

engine layer to improve the execution speed of count() and sum().● Kill idle transactions: Transactions that have been idled for a long time are

automatically killed after the timeout threshold is reached.● Support show full processlist queries for memory usage and CPU usage of

user threads.

MySQL 5.6

20191215

New features

● Long transactions: Obtain the transaction execution time Trx_Executed_Timethrough SHOW PROCESSLIST.

● Online extension of the String field length: Extend the VARCHAR field lengthfrom COPY to INPLACE.

20191015

New features

● Upgrade the minor version to 5.6.45.● Support show full processlist queries for memory usage and CPU usage of

user threads.● Kill idle transactions: Transactions that have been idled for a long time are

automatically killed after the timeout threshold is reached.● SQL filtering: Set SQL statements to filter out the SQL statements that are not

processed. This function ensures the stability of core services during peakhours.

20190815

New features



● Logical read-ahead: During a full table scan query or range scan query, logicalread-ahead accelerates the execution speed and reduces disk I/Os.

● Jemalloc memory management: Replace the jlibc memory managementmodule to reduce the memory usage and improve memory allocationefficiency.

20190615

New features

● Upgrade the minor version to 5.6.43.● Support the audit function.● Support implicit primary keys: If a user does not specify a primary key or

unique index when creating a table, the system automatically creates animplicit primary key to resolve the primary/standby replication delay causedby no primary keys.

20190515

Fixed bugs

● The replication delay second_behind_master is inaccurate in certainscenarios.

● The replication delay is abnormal when SQL_MODE is set toPAD_CHAR_TO_FULL_LENGTH.

20190115

Fixed bugs

● After the flush operation is performed on read replicas, data replication isinterrupted and data is inconsistent between primary and standby DBinstances.

● The replication thread of the standby database is deadlocked due to theREPAIR or OPTIMIZE statements.

● Errors occur on the grant select(column_name) statement replicationthreshold.

20181115

New features

● Upgrade the minor version to 5.6.41.● Support creation and deletion of temporary tables in transactions when GTID

is enabled.● Support table-level MTS parallel playback.

20180715

● New features– Upgrade the minor version to 5.6.40.– Support thread pools.– Support the CTS syntax: create table xx select.

● Fixed bugs



– Binlog and relay log names depend on the PID file names.– The relay_log_basename parameter is not specified, resulting in the

failure of primary/standby replication.– The force index syntax becomes invalid in the group_by xx order_by xx

limit n1,n2 scenario.



12 Function Differences of RDS for SQLServer DB Instances

This section describes function differences between single and primary/standby DBinstances as well as function differences among SQL Server editions.

● For details about differences of basic functions, see Table 12-1.● For details about differences of product functions, see DB Instance

Introduction.● For details about differences of database migration functions, see Table 12-2.● For details about differences of database security functions, see Table 12-3.

Table 12-1 Differences of basic functions

Module Function Item Primary/Standby Single

Life cycle Create a DBinstance

Supported Supported

Reboot a DBinstance

Supported Supported

Auto-renewal Supported Supported

Change the billingmode

Supported Supported

Change theinstance class

Supported Supported

Delete a DBinstance

Supported Supported

Upgrade the DBengine version

Supported Supported

Restore to a newDB instance

Supported Supported

Relational Database ServiceService Overview

12 Function Differences of RDS for SQL Server DBInstances


https://support.huaweicloud.com/en-us/productdesc-rds/rds_01_0010.html

https://support.huaweicloud.com/en-us/productdesc-rds/rds_01_0010.html


Create a readreplica

Supported (for2017 EE only)

Not supported

DB instanceproperties

View the DBinstance list

Supported Supported

View DB instancedetails

Supported Supported

Modify the DBinstancedescription

Supported Supported

Change themaintenancewindow

Supported Supported

Manage tags Supported Supported

Manage AZs Not supported Not supported

Databaseconnection

Internal accessthrough a VPC

Supported Supported

Public accessibility Supported Supported

Read/write splittingaddress


Serviceavailability

Disaster recovery inan AZ

Supported Supported

Disaster recovery inthe same city

Supported Not supported

Remote disasterrecovery


Disaster recoverydrill


Backups andrestorations

Full backup Supported Supported

Log backup Supported Supported

Customize abackup policy

Supported Supported

Restore fromautomated backups

Supported Supported

Point in timerecovery

Supported Supported

Partial backup Supported Supported

Partial restore Supported Supported





Monitoringand alarms

Resourcemonitoring

Supported Supported

DB enginemonitoring


Customizemonitoring policies

Supported Supported

Aggregatemonitoring items

Supported Supported

Parametermanagement

Parameter update Supported Supported

Parametertemplate

Supported Supported

Logmanagement

Error logs Supported Supported

System runninglogs

Supported Supported

Table 12-2 Differences of database migration


Homogeneousdata migration

Supported Supported

Heterogeneousdata migration


Datasynchronization

Supported Supported

Table 12-3 Differences of database security


IP addresswhitelist


Managementaudit

Supported Supported

Firewall Supported (DBSS) Supported (DBSS)

Database audit Supported (DBSS) Supported (DBSS)

Storageencryption

Supported Supported





Networkencryption

Supported Supported

Security groupmanagement

Supported Supported

TransparentData Encryption(TDE)encryption

Supported (Enterprise Edition) Supported (EnterpriseEdition)

Table 12-4 lists the major differences of the official Microsoft SQL Server editions.

For more information about function differences among Microsoft SQL Server2014 official editions, see official documents.

For more information about function differences among Microsoft SQL Server2016 official editions, see official documents.

Table 12-4 Differences of Microsoft SQL Server editions

Function Item Web Edition Standard Edition EnterpriseEdition

Instance class 16 vCPUs | 64GB

16 vCPUs | 128 GB(Microsoft SQL Server2012 and 2014)24 vCPUs | 128 GB(Microsoft SQL Server2016 and 2017)

60 vCPUs | 512GB




https://docs.microsoft.com/en-us/sql/getting-started/features-supported-by-the-editions-of-sql-server-2014?view=sql-server-2014

https://docs.microsoft.com/en-us/sql/sql-server/editions-and-components-of-sql-server-2016?view=sql-server-2017


High availability Not supported Mirror HA ● MicrosoftSQLServer2008(Mirror)

● MicrosoftSQLServer2012(Mirror)



● MicrosoftSQLServer2017(AlwaysOn)

Data compression Supported Supported Supported

SQL Profiler Supported Supported Supported

Column index Not supported Supported Supported

Table/indexpartitioning

Supported ● Microsoft SQL Server2014

● Microsoft SQL Server2016


● Not supported forMicrosoft SQL Server2008

Supported

Change DataCapture (CDC)

Not supported ● Microsoft SQL Server2016


Supported

Online DDL Not supported Not supported Supported

Parallel searches Not supported Not supported Supported





Adjustment ofpartitioned tableparallelism

Not supported Not supported Supported

TDE Not supported Not supported Supported

Advanced Rintegration

Not supported Not supported Supported




A Change History

Released On Description

2020-03-31 This issue is the eighteenth officialrelease, which incorporates thefollowing change:Added Billing.

2020-03-06 This issue is the seventeenth officialrelease, which incorporates thefollowing change:Supported PostgreSQL 12.

2019-12-30 This issue is the sixteenth officialrelease, which incorporates thefollowing change:Added section DamengDB Constraints.

2019-12-15 This issue is the fifteenth officialrelease, which incorporates thefollowing change:Added the MySQL minor versiondescription from 20191015 to20191215.

2019-10-31 This issue is the thirteenth officialrelease, which incorporates thefollowing change:Added section DB Instance StorageType.

2019-10-12 This issue is the twelfth official release,which incorporates the followingchange:Added section RDS for MySQLVersion Description.

Relational Database ServiceService Overview A Change History



2019-09-12 This issue is the eleventh officialrelease, which incorporates thefollowing change:Supported Kunpeng generalcomputing-plus DB instancespecifications.Supported General-enhanced II DBinstance specifications.Supported MySQL 8.0.Supported Microsoft SQL Server 2017Standard Edition and 2017 WebEdition.

2019-06-12 This issue is the tenth official release,which incorporates the followingchange:Added Permissions Management.

2019-01-08 This issue is the ninth official release,which incorporates the followingchanges:SQL Server 2012 is added.

2018-11-20 This issue is the eighth official release,which incorporates the followingchange:Supported I3 specifications forPostgreSQL.

2018-10-15 This issue is the seventh officialrelease, which incorporates thefollowing changes:● Supported finance edition of

MySQL DB instances.● Supported "Always On" primary/

standby DB instances for MicrosoftSQL Server.




2018-08-15 This issue is the sixth official release,which incorporates the followingchanges:● Added the I3 DB instance

specifications.● Supported 2 vCPUs | 4 GB

specifications for three MicrosoftSQL Server Web Editions.

● Supported the following MicrosoftSQL Server 2008 Enterprise Editionspecifications: 2 vCPUs | 4 GB, 16vCPUs | 64 GB, 32 vCPUs | 256 GB,and 60 vCPUs | 512 GB.

2018-07-13 This issue is the fifth official release,which incorporates the followingchange:● Supported SQL Server 2016 Web.● Supported SQL Server 2014 SP2

Web.● Supported SQL Server 2008 R2 SP3

Web.

2018-06-30 This issue is the fourth official release,which incorporates the followingchange:Added descriptions of RDS DB engines.

2018-06-15 This issue is the third official release,which incorporates the followingchanges:● Increased the backup retention

period to 732 days.● Supported 1 vCPU | 2 GB and 1

vCPU | 4 GB instance classes forPostgreSQL DB instances.




2018-06-01 This issue is the second official release,which incorporates the followingchanges:● Supported DSS.● Supported a maximum of 4000 GB

of storage space when you createor scale up a DB instance.

● Supported creating yearly/monthlyDB instances in batches.

● Supported PostgreSQL 10.● Supported Microsoft SQL Server

2008 R2 SP3 Enterprise Edition.

2018-05-15 This issue is the first official release.



Documents

Service Overview Overview.pdfRelational Database Service Service Overview Issue 18 Date 2020-03-31 HUAWEI TECHNOLOGIES CO., LTD