Feature | Description |
Log In | Click Log In in the Operation column to log in to the database using the next-generation database tool. For more information, see DMC Overview. |
Manage | Click Manage in the Operation column to enter the instance management page. |
Upgrade Version | Two-node and three-node instances: Click More > Upgrade Version in the Operation column to upgrade the database version. For more information, see Upgrading Database Engine Versions. Single-node and Cluster Edition instances: Upgrading the database engine version is not yet supported. |
Purchase Same Configuration | After the target instance is selected, click More > Purchase Same Configuration in the Operation column to quickly create a new instance with the same configuration as the selected one on the purchase page. |
Adjust Configurations | Click More > Adjust Configurations in the Operation column to adjust the configuration of the database instance (scaling). Both instance upgrade and downgrade are supported. For more information, see Adjusting Database Instance Specifications. For Cluster Edition instances, you can also quickly add and delete read-only nodes by adjusting the configuration. For more information, see Adjusting Instance Configuration. |
Pay-as-You-go to Monthly Subscription | Click More > Pay-as-You-Go to Monthly Subscription in the Operation column to change the billing mode of pay-as-you-go instances. For more information, see Pay-as-You-Go to Monthly Subscription. |
Edit Tag | Click More > Edit Tag in the Operation column to edit and manage the tags of instance resources. For more information, see Tag Editing. |
Terminate/Return | Click More > Terminate/Return in the Operation column to return the instance by yourself. For more information, see Terminating an Instance. |
Security Group | Click More > Security Group in the Operation column to configure or modify the security group of the instance. For more information, see Cloud Database Security Group Management. |
Create | Click Create above the instance list to go to the purchase page and create an instance. For more information, see Creating a MySQL Instance. |
Renew | After the target instance is selected, click Renew above the instance list to manually renew the instance. For more information, see Renewal Instructions. |
Restart | After the target instance is selected, click Restart above the instance list to restart the instance. Batch restart is supported (selecting multiple instances). During the restart, the instances will not be accessible normally and existing connections will be disconnected. Please be prepared to avoid any impact. Restart will fail if there are a large number of writes and dirty pages during the restart. In this case, the instance will roll back to the status before the restart and can still be accessed. Be sure to restart the instance during off-hours so as to ensure success and reduce the impact on your business. |
Roll Back | After the target instance is selected, click More > Roll Back above the instance list to roll back a database to a specified time based on backups. For more information, see Rolling Back a Database. |
Parameter Settings | After the target instance is selected, click More > Parameter Settings above the instance list to modify the parameter values of the instance. Batch settings are supported (selecting multiple instances). For more information, see Setting Instance Parameters. |
Enable Auto-Renewal | After the target instance is selected, click More > Enable Auto-Renewal above the instance list to make the non-auto-renewal instance automatically renew monthly after expiration. Batch enablements are supported (selecting multiple instances). For more information, see Renewal Instructions. |
Disable Auto-Renewal | After the target instance is selected, click More > Disable Auto-Renewal above the instance list to cancel auto-renewal for instances that are already set to auto-renew. Batch cancellations are supported (selecting multiple instances). |
Quick Migration | After the required target instance is selected, click Quick Migration above the instance list to migrate TencentDB for MySQL two-node/three-node instances to TDSQL-C for MySQL. For more information, see Perform Quick Migration. |
Quick Check | Click Quick Check above the instance list to go to the TencentDB for DBbrain Console, where you can view the health status of instances under your account and perform performance optimization on instances. For more details, see MySQL Performance Optimization. |
Comparative Monitoring | After 2 to 6 target instances are selected, click Comparative Monitoring above the instance list to view and compare the monitoring situation of multiple instances in the pop-up window on the right side of the console. |
Feature Page | Feature Item | Description |
Instance Details | Viewing instance health status | Help users find the abnormal situation of the instance in time and optimize system performance and security configurations. For more information, see Viewing Instance Health Status. |
| Setting instance maintenance time | The system will aperiodically perform maintenance on instances during the maintenance time. For more information, see Setting Instance Maintenance Time. |
| Assigning instances to projects | Assign instances to different projects for management. For more information, see Assigning Instances to Projects. |
| Adjusting database instance specifications | Quickly adjust instance specifications through the console for flexible scaling. For more information on single-node, two-node, and three-node instances, see Adjusting Database Instance Specifications. For more information on Cluster Edition instances, see Adjusting Instance Configuration. |
| Modifying the port number | Support modification of the port number for the instance's private network address. For more information on single-node, two-node, and three-node instances, see Modifying the Port Number. For more information on Cluster Edition instances, see Read-Write Address Management and Read-Only Address Management. |
| Migrate to New AZ | Migrate TencentDB for MySQL instances to another availability zone in the same region. For more information, see Migrating Availability Zones. |
| Source/Replica Switch | Switch the primary and secondary databases of instances. For more information on two-node and three-node instances, see Primary/Replica Switch. For more information on Cluster Edition instances, see Primary/Replica Switch. |
| CPU elastic scale-out | Automatically or manually expand the CPU upper limit of the current instance. For more information, see CPU Elastic Scale-out. Cluster Edition instances do not support this feature. |
| Managing disaster recovery instances | Two-node and three-node instances support the creation of disaster recovery instances. For more information, see Managing Disaster Recovery Instances. Single-node and Cluster Edition instances do not support the creation of disaster recovery instances. |
| Network switch | Modify the private network of instances. For more information on single-node, two-node, and three-node instances, see Network Switch. For more information on Cluster Edition instances, see Read-Write Address Management and Read-Only Address Management. |
| Enabling public network connection address | |
Instance Monitoring | | You can view the monitoring of many core metrics of the current database in dimensions such as access, load, query cache, Ttable, InnoDB, and MyISAM. For details, see Monitoring Features and Alarm Feature. Cluster Edition instances support switching nodes on the instance monitoring page to view the monitoring situation. For more information, see View Instance Monitoring. |
Database Management | Database List | The DMC console allows you to create databases and tables, manage databases, import/export data, and supports SQL window. For more information, see DMC Management. |
| Parameter Settings | View and modify some parameters through the console, and query parameter modification records in the console. For more information on single-node, two-node, and three-node instances with 4 cores and above, see Intelligent Parameter Tuning. Cluster Edition instances currently do not support intelligent parameter tuning. |
| Account Management | You can manage the default root account of the system or create and manage new accounts. |
Security Group | | You can configure security groups for your databases. For more information, see TencentDB Security Group Management. |
Backup and Restoration | Back up a database | You can automatically or manually back up the database. For more information, see Back up a Database. |
| Configuring transition-to-cold storage | Support transition-to-cold storage for backup files to reduce backup storage costs. For more information on two-node and three-node instances, see Configuring Transition-to-Cold Storage. Single-node and Cluster Edition instances currently do not support configuring transition-to-cold storage. |
| Cross-Region Backup | Support storing backup files in another region. For more information on two-node, three-node, and Cluster Edition instances, see Cross-Region Backup. Single-node instances currently do not support cross-region backup. |
| Backup Encryption | Support encryption of physical backups and log backups (binlog). For more information on two-node and three-node instances, see Backup Encryption. Single-node and Cluster Edition instances currently do not support backup encryption. |
| Setting backup download rules | Set restrictions for backup download. For more information on two-node and three-node instances, see Setting Backup Download Rules. Single-node and Cluster Edition instances currently do not support setting backup download rules. |
| Viewing backup space | |
| Setting local Binlog retention | Set the binlog retention period for the instance. For more information, see Setting Local Binlog Retention. Single-node instances do not support setting local binlog retention. |
| Restoring a database using physical backup | Two-node and three-node instances support the use of XtraBackup tool to restore MySQL physical backup files to a self-built database on another host. For more information, see Restoring a Database Using Physical Backup. |
| Restoring a database using logical backup | Two-node and three-node instances support using logical backup files for manual data restoration. For more information, see Restoring a Database Using Logical Backup. |
| Downloading a backup | Logical and physical backups of two-node and three-node instances can be downloaded. For more information, see Downloading a Backup. Snapshot backups of single-node and Cluster Edition instances cannot be downloaded. |
| Rolling back a database | Data corrupted can be recovered through rollback in a self-service manner. For more information, see Rolling back a Database. |
| Deleting a backup | Only manual backup files of two-node and three-node instances can be deleted. For more information, see Delete a Backup. |
| Cloning an instance | Help users quickly roll back an instance to a newly purchased MySQL instance. For more information, see Cloning an Instance. |
Operation Log | | For Cluster Edition, two-node, and three-node instances, slow logs, error logs, and rollback logs can be viewed, and logs can be shipped. For more information, see Operation Logs and Log Shipping. For single-node instances, slow logs and error logs can be viewed. For more information, see Operation Logs. |
Read-Only Instance | Creating a read-only instance | Create one or more read-only instances to support users' read-write separation and one-primary-multiple-secondary application scenarios. For more information on two-node and three-node instances, see Creating a Read-Only Instances. For Cluster Edition instances, 1-5 read-only nodes can be created. For more information, see Adding a Node for an Instance. For Cluster Edition instances, 1-15 independent read-only instances can also be created. For more information, see Creating a Read-Only Instance. |
| Managing the RO group of read-only instance | Two-node and three-node instances support managing the RO group of read-only instance. For more information, see Managing RO Group of Read-Only Instance. |
| Managing delayed replication of read-only instance | Two-node and three-node instances support managing delayed replication of read-only instances. For more information, see Managing Delayed Replication of Read-Only Instance. |
Database Proxy | | It is used to proxy requests when the application server accesses the database. It provides advanced features such as automatic read/write separation, connection pool, and connection retention. Single-node and Cluster Edition instances do not support database proxy. For more information on two-node and three-node instances, see Database Proxy Overview. |
Data Security | Enabling Transparent Data Encryption (TDE) | Two-node and three-node instances support enabling TDE. For more information, see Enabling Transparent Data Encryption. |
| Setting SSL encryption | Two-node and three-node instances support setting SSL encryption. For more information, see Setting SSL Encryption. |
Connection Check | | You can detect potential connection access issues with your TencentDB and address them using the provided solutions to ensure that your TencentDB can be accessed normally. For more information, see One-Click Connectivity Checker. |
Was this page helpful?