To ensure instance stability and security, ApsaraDB RDS for MySQL has some service limits.
Limits of other database engines are listed as follows:
- Limits of ApsaraDB RDS for SQL Server
- Limits of ApsaraDB RDS for PostgreSQL
- Limits of ApsaraDB RDS for PPAS
- Limits of ApsaraDB RDS for MariaDB
The following tables lists the limits of ApsaraDB RDS for MySQL.
|Instance parameters||Instance parameters can be modified through the RDS console or API operations. Due to security and stability considerations, only specific parameters can be modified. For more information, see Use the console to set parameters.|
|Root permissions of databases||The root or system administrator permissions are not provided.|
|ApsaraDB RDS for MySQL storage engine||Only InnoDB is supported.
|Database replication||ApsaraDB RDS for MySQL provides a primary/secondary replication architecture (except in the Basic Edition). The secondary instance in the architecture is hidden and cannot access your applications.|
|Instance restart||Instances must be restarted through the RDS console or API operations.|
|Network settings||If a MySQL 5.5 or 5.6 instance is in the classic network and the database proxy mode is enabled for it, you are not allowed to enable net.ipv4.tcp_timestamps in SNAT mode.|
If the storage space usage for an instance is abnormally high, the system will lock the instance to prevent data loss that may occur due to incorrect operations. You can unlock the instance by upgrading the instance specifications.
|Help information||You cannot query help topic details because the mysql.help_topic table is empty.|