What's New
The tables below describe the features released in each TaurusDB version and corresponding documentation updates. New features will be successively launched in each region.
May 2025
| No. | Feature | Description | Phase | Document |
|---|---|---|---|---|
| 1 | APIs for quickly querying and killing sessions | APIs for quickly querying and killing sessions are available. | Commercial use |
August 2024
| No. | Feature | Description | Phase | Document |
|---|---|---|---|---|
| 1 | Sessions | You can view current session statistics of your instance and kill abnormal sessions. | Commercial use | |
| 2 | Auto throttling | Auto throttling allows you to kill all sessions, kill specific sessions by criteria, and view history. | Commercial use |
May 2024
| No. | Feature | Description | Phase | Document |
|---|---|---|---|---|
| 1 | Rebooting a proxy instance | You can reboot a proxy instance as needed. | Commercial use |
February 2024
| No. | Feature | Description | Phase | Document |
|---|---|---|---|---|
| 1 | Storage analysis in DBA Assistant | On the Storage Analysis page, you can view the distribution and change trend of the disk space. | Commercial use |
November 2023
| No. | Feature | Description | Phase | Document |
|---|---|---|---|---|
| 1 | Searching for databases | You can search for desired databases on the Databases page. | Commercial use |
August 2023
| No. | Feature | Description | Phase | Document |
|---|---|---|---|---|
| 1 | Setting the backup retention period to 3,660 days | When configuring an automated backup policy, you can set the retention period to 1 to 3,660 days. | Commercial use |
May 2023
| No. | Feature | Description | Phase | Document |
|---|---|---|---|---|
| 1 | Recycle bin | You can move deleted instances to the recycle bin. The recycle bin is enabled by default and cannot be disabled. | Commercial use | |
| 2 | Changing a node name | You can change a node name for easy identification. | Commercial use |
February 2023
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.