Constraints

Storage space

• Pay-per-use instance: a maximum of 128,000 GB
• Yearly/monthly instance: 40 GB to 128,000 GB
• Serverless instance: a maximum of 128,000 GB
• Standard HTAP instance: 50 GB to 32,000 GB for backend nodes; 50 GB to 1,000 GB for frontend nodes

-

Temporary disk space

500 GB at most

For more information, see How Can I Use Temporary Disk of TaurusDB?

Connections

TaurusDB does not have constraints on the number of connections. It depends on the default values and value ranges of certain parameters in your DB engine.

For more information, see What Is the Maximum Number of Connections to a TaurusDB Instance?

TaurusDB instances

50 instances at most

For details about how to increase the quota, see Increasing Quotas.

Read replicas

• A single yearly/monthly instance: 0 to 15 read replicas
• A single pay-per-use instance: 0 to 15 read replicas
• A single serverless instance: 0 to 7 read replicas

For more information, see Introducing Read Replicas.

Tags

A maximum of 20 tags for each instance

For more information, see Tag Management.

Free backup space

About 100% of the purchased storage space

For more information, see How Is TaurusDB Backup Data Billed?

Automated backup retention period

• Same-region backup: 1 to 732 days (7 days by default) You can contact customer service to extend the retention period to 3,660 days.
• Cross-region backup: 1 to 1,825 days

For more information, see Configuring a Same-Region Backup Policy and Configuring a Cross-Region Backup Policy.

Log retention period

• Error logs: 30 days
• Slow query logs: 30 days
• Slow query logs in plaintext: 30 days

For more information, see Log Management.

Instance name

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

For more information, see Changing a DB Instance Name.

Database name

• The database name must consist of 1 to 64 characters. Only letters, digits, hyphens (-), and underscores (_) are allowed. The total number of hyphens (-) cannot exceed 10.
• To prevent errors, reserved keywords cannot be used.

For more information, see Creating a Database.

Username

• The username must consist of 1 to 32 characters. Only letters, digits, and underscores (_) are allowed.
• To prevent errors, reserved keywords cannot be used.

For more information, see Creating an Account.

Parameter template name

The template name must consist of 1 to 64 characters. Only letters (case-sensitive), digits, hyphens (-), underscores (_), and periods (.) are allowed.

For more information, see Creating a Parameter Template.

Backup name

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

For more information, see Creating a Manual Backup.

Table name/function name/stored procedure name/view name

To prevent errors, reserved keywords cannot be used.

For more information, see Database Table Usage.

Database root permissions

Only the root user is available on the instance creation page.

-

Account password

• It must consist of 8 to 32 characters.
• It must contain at least three types of the following characters: uppercase letters, lowercase letters, digits, and special characters (~!@#$%^*-_=+?,()&|.).
• It cannot be the username or the username spelled backwards.
• It must comply with the values of validate_password parameters.

  To check the password-related parameter values, click an instance name, choose Parameters in the navigation pane, and search for validate_password in the upper right corner of the page.

For more information, see Resetting the Administrator Password.

Port

• The default value is 3306 and can be changed manually.
• The database port ranges from 1025 to 65534, excluding 5342, 5343, 5344, 5345, 12017, 20000, 20201, 20202, 33062, 33060, and 33071, which are reserved by the system.

For more information, see Changing a Database Port.

VPC

After a TaurusDB instance is created, the VPC cannot be changed.

-

Security group

• By default, you can create a maximum of 100 security groups in your cloud account.
• By default, you can add a maximum of 50 rules to a security group.
• One TaurusDB instance can be bound to multiple security groups, and one security group can be associated with multiple TaurusDB instances.
• When creating an instance, you can select multiple security groups. (For better network performance, you are advised to select at most five security groups.)

-

System accounts

To provide O&M services, the system automatically creates system accounts when you create TaurusDB instances. These system accounts are unavailable to you.

• rdsAdmin: a management account with highest permissions, which is used to query and modify instance information, rectify faults, migrate data, and restore data.
• rdsRepl: a replication account, which is used to synchronize data from primary nodes to standby nodes or read replicas.
• rdsBackup: a backup account, which is used to back up data in the background.
• rdsMetric: a metric monitoring account, which is used by watchdog to collect database status data.
• rdsProxy: a database proxy account, which is used for authentication when the database is connected through a proxy address. This account is automatically created when you create a proxy instance.

-

Instance parameters

Most parameters can be modified through the console or APIs. To ensure security and stability of instances, some parameters cannot be modified.

For more information, see Modifying Parameters of a DB Instance.

MySQL storage engine

TaurusDB supports only the InnoDB storage engine.

-

TaurusDB access

• If TaurusDB instances do not have EIPs bound, the instances must be in the same VPC as the ECSs associated with these instances.
• Security group rules must be added to allow ECSs to access TaurusDB instances.

  By default, a TaurusDB instance cannot be accessed by an ECS in a different security group. To enable access, you must add an inbound rule to the security group of a TaurusDB instance. When adding the rule, set the protocol and port, respectively, to TCP and to the default database port of the instance.

• Port of a TaurusDB instance:

  The default port is 3306. You can change it if you want to access a TaurusDB instance through another port over a private or public network. For details, see Changing a Database Port.

-

Data migration

DRS or mysqldump can be used to migrate data to TaurusDB.

For more information, see Data Migration.

TaurusDB instance reboot

Instances can only be rebooted on the TaurusDB console.

For more information, see Rebooting a DB Instance.

TaurusDB backups

TaurusDB backups are stored in OBS buckets and are not visible to you.

-

Binlog function

Binlog cannot be enabled for TaurusDB read replicas.

For more information, see How Do I Enable and View Binlog of My TaurusDB Instance?

Partitioned tables

TaurusDB is compatible with MySQL Community Server 8.0.22. For a list-partitioned table, there are a maximum of 256 values in a partition, or an error is reported. (Workaround: Redistribute the contents of one table partition into multiple partitions.)

-

Small-scale instances

For TaurusDB instances with 2 vCPUs and 8 GB memory, there are a maximum of 300,000 tables in a single instance and a maximum of 5,000 tables in a single database.

-