It generally takes less than 10 minutes to create a TencentDB instance. The time it takes to create read-only instances is subject to the data volume of the master instance. The larger the data volume, the longer the time.
If it takes longer to create an instance, there may be something wrong. Please contact us promptly.
You can log in to the TencentDB for MySQL Console and select More > Terminate/Return or Terminate/Return & Refund in the "Operation" column in the instance list to return an instance. For more information, please see Terminating Instance.
When an instance is returned, it will be retained in the recycle bin for a period of time. A monthly subscription instance will be retained for 7 days and a pay-as-you-go instance for 1 day. During this period, you can go to the recycle bin and restore the instance.
You can view the maximum number of connections to TencentDB for MySQL in the console. If the number of connections gets too high, you are recommended to locate the cause and solve the problem first instead of directly increasing the maximum value.
Log in to the TencentDB for MySQL Console, click an instance name to enter the instance management page, select Database Management > Parameter Settings, and modify the
max_connections represents the allowed maximum connections in instance monitoring. You can customize the maximum value up to 10,240. Number of open connections means the number of connections available at the current moment, a value that changes in real time.
The monitoring center oversees the disk space of a TencentDB instance. When the disk utilization is over 90%, SMS and email alarms will be triggered. To receive such alarms, you only need to configure alarm recipients in Cloud Monitor. (For more information on how to configure, please see Alarming Feature).
You need to adjust the
lower_case_table_names parameter of the database.
Log in to the TencentDB for MySQL Console, click the instance name to enter the instance management page, select Database Management > Parameter Settings, and modify the
lower_case_table_names parameter (0: case-sensitive, 1: case-insensitive).