- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Best Practice
- Security White Paper
- Development Guide
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Instance Management APIs
- UpgradeDedicatedDBInstance
- ModifyBackupTime
- OpenDBExtranetAccess
- DescribePrice
- ModifyDBInstancesProject
- DescribeFlow
- CloseDBExtranetAccess
- CreateDBInstance
- DescribeBackupTime
- DescribeDBInstances
- InitDBInstances
- ModifyDBInstanceName
- DescribeInstanceNodeInfo
- DescribeDcnDetail
- DestroyHourDBInstance
- CancelDcnJob
- CreateHourDBInstance
- SwitchDBInstanceHA
- IsolateHourDBInstance
- ActivateHourDBInstance
- DestroyDBInstance
- ModifyInstanceVport
- ModifyInstanceVip
- ModifyInstanceNetwork
- IsolateDedicatedDBInstance
- IsolateDBInstance
- TerminateDedicatedDBInstance
- DescribeDBInstanceDetail
- DescribeOrders
- Parameter Management APIs
- Monitoring Management APIs
- Backup and Restoration APIs
- Account APIs
- Security Group APIs
- Other APIs
- Data Types
- Error Codes
- FAQs
- General References
- Glossary
- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Best Practice
- Security White Paper
- Development Guide
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Instance Management APIs
- UpgradeDedicatedDBInstance
- ModifyBackupTime
- OpenDBExtranetAccess
- DescribePrice
- ModifyDBInstancesProject
- DescribeFlow
- CloseDBExtranetAccess
- CreateDBInstance
- DescribeBackupTime
- DescribeDBInstances
- InitDBInstances
- ModifyDBInstanceName
- DescribeInstanceNodeInfo
- DescribeDcnDetail
- DestroyHourDBInstance
- CancelDcnJob
- CreateHourDBInstance
- SwitchDBInstanceHA
- IsolateHourDBInstance
- ActivateHourDBInstance
- DestroyDBInstance
- ModifyInstanceVport
- ModifyInstanceVip
- ModifyInstanceNetwork
- IsolateDedicatedDBInstance
- IsolateDBInstance
- TerminateDedicatedDBInstance
- DescribeDBInstanceDetail
- DescribeOrders
- Parameter Management APIs
- Monitoring Management APIs
- Backup and Restoration APIs
- Account APIs
- Security Group APIs
- Other APIs
- Data Types
- Error Codes
- FAQs
- General References
- Glossary
October 2022
Update | Description | Documentation |
Supported adding account permission | You can grant the RELOAD permission for the account for NewDTS data migration. | |
Supported downgrade for disaster recovery read-only instances | You can downgrade the disaster recovery read-only instances in the console. | |
Optimized the display of available regions | You can view the region where resources are sold out when selecting a region, and select a random AZ in the console. | - |
September 2022
Update | Description | Documentation |
Backup time optimization | The backup can be retained for 365 days and performed at your selected time. | |
Backup search optimization | You can filter the cold backup list, binlog list, slow query, and error log by time. | |
Newly supported version for data encryption | TencentDB for MySQL 8.0 supports Transparent Data Encryption (TDE). | |
Supported creating database in CDC | You can create MariaDB instances in CDC and manage them in the console. | |
July 2022
Update | Description | Documentation |
Public network security group | For instances with public network address enabled in Guangzhou, Chengdu, Shanghai, Beijing, Nanjing, security groups support public network access. | |
Supported InnoDB page size setting when purchasing an instance | InnoDB page size is set to 16 KB by default, and it cannot be modified once the instance is created. Select a page size with caution. | - |
Supported setting max connections for creating an account | The number of concurrent connections under this account is subjected to the maximum connections of the instance and can be set when creating an account for TencentDB for MariaDB 5.6 and 8.0. | |
Supported setting replica connection mode for read-only account | When setting the connection mode for read-only account, you can decide whether to switch to another replica if the primary-replica delay exceeds the delay parameter. |
January 2022
Update | Description | Documentation |
Supported rollback to pay-as-you-go instances | The database rollback feature is updated, so data will be rolled back to pay-as-you-go instances instead of temp instances. After rollback to a pay-as-you-go instance, you can flexibly configure the retention time of the rollback instance based on your business needs. Rollback instances have the same functionality, security, and reliability as general instances. | |
Supported modifying the parameters for disaster recovery read-only instances | You can modify the parameters for disaster recovery read-only instances in the console. | - |
December 2021
Update | Description | Documentation |
Supported AZ migration | The AZ migration feature is launched. It can implement nearby access and resource expansion for your business and better utilize resources in different AZs in the same region. | - |
Supported custom old IP retention period | When switching IP manually, you can customize the old IP retention period. In this way, IP resources can be released quickly or retained for a long time to allow for business migration. | |
Supported modifying the read-only policy | You can modify the policy of a read-only account to satisfy different read-only access and delay requirements. |
March 2021
Update | Description | Documentation |
Cloud Monitor optimization | TencentDB for MongoDB now works with the latest version of Cloud Monitor, supporting dashboards, more monitoring metrics, and default alarms. The metric names are modified to better follow the naming conventions; and you can now use Cloud Monitor APIs to fetch TencentDB for MongoDB monitoring data. | |
One-primary-multi-replica instances are supported | You can now create an instance with one primary node and up to five replica nodes, so as to provide higher data availability. | - |
Supported modifying VPC configurations | You can now modify the access address of an instance via network translation. |
October 2020
Update | Description | Documentation |
Supported disaster recovery read-only instances | You can quickly create disaster recovery read-only instances in the console for data deployment and disaster recovery capability across regions and AZs | |
Supported instance architecture diagram. | You can view instance region, nodes, shards, and primary-replica relationship, or create a disaster recovery read-only instance sync in the instance architecture diagram in the console. | - |
August 2020
Update | Description | Documentation |
Supported MySQL 8.0 | You can now purchase TencentDB for MariaDB instances running the MySQL 8.0 kernel. Such instances support multi-thread async replication (MAR, namely strong sync), thread pools (enabled by default), and async deletion of big tables. | - |
Supported tags | You can manage TencentDB for MariaDB instances by tag. | - |
Supported DMC | You can now manage TencentDB for MariaDB instances in DMC. | - |
Other features | You can now download the latest binlog, split and analyze it. Related user interactions in the console are optimized. | - |
June 2015
Update | Description | Documentation |
TencentDB for MariaDB is officially launched | TencentDB for MariaDB is a highly secure enterprise-grade cloud database dedicated to the online transaction processing (OLTP) scenario. It has always been used in Tencent's billing business. It is compatible with MySQL syntax and has various advanced features such as thread pool, audit, and remote disaster recovery while delivering easy scalability, simplicity, and high cost efficiency of TencentDB. |
Yes
No
Was this page helpful?