One-stop database automatic management system based on DevOps concept

Abstract

The invention provides a one-stop database automatic management system based on a DevOps concept, and belongs to the technical field of databases, the one-stop database automatic management system comprises an SQL auditing module for providing an auditing process panel, and realizing SQL automatic auditing and manual SQL auditing based on an SQL suggestion module and a GitOps workflow module. And the SQL suggestion module provides an SQL suggestion rule engine which is used by the SQL auditing module and the SQL editor module. And the SQL editor module provides a visual operation page for a developer to execute SQL and provides SQL suggestions for the developer in real time based on the SQL suggestion module. And the GitOps workflow module provides an integrated third-party Git project management tool to realize the combination of database development and operation and maintenance. The backup recovery module provides diversified backup mechanisms, and database operation and maintenance burdens are relieved for developers.

Description

Technical Field

[0001] The present invention relates to the technical field of databases, and in particular to a one-stop database automation management system based on the DevOps concept. Background Art

[0002] DevOps is a software engineering practice method aimed at improving the speed, quality, and reliability of software delivery by promoting collaboration between development teams and operations teams. It originated from the agile software development methodology, emphasizing automated IT processes, team collaboration and communication, continuous integration, and continuous delivery (CI / CD) to achieve more efficient and reliable software delivery.

[0003] In traditional database management, many operations need to be performed manually, such as performance tuning, backup and recovery, data migration, etc. This is not only inefficient but also error-prone. The one-stop database automation management method based on the DevOps concept realizes the full automation of database management by integrating the practices of DevOps and DataOps. This method uses technologies such as automation scripts, configuration management, and continuous integration to automate the deployment, monitoring, optimization, and fault handling of databases, thus significantly improving the efficiency and accuracy of database management.

[0004] In addition, with the development of cloud computing and containerization technologies, this automation management method has been further strengthened. Container technology makes the deployment and operation of databases more lightweight and flexible, while cloud services provide the ability to elastically expand and allocate resources on demand. These technological advancements provide strong technical support for database automation management based on the DevOps concept. Summary of the Invention

[0005] To solve the above technical problems, the present invention provides a one-stop database automation management system based on the DevOps concept.

[0006] The technical solution of the present invention is as follows:

[0007] A one-stop database automation management system based on the DevOps concept, comprising:

[0008] The SQL audit module provides an audit process panel and realizes automatic SQL audit and manual SQL audit based on the SQL recommendation module and the GitOps workflow module;

[0009] The SQL recommendation module provides an SQL recommendation rule engine for use by the SQL audit module and the SQL editor module;

[0010] The SQL editor module provides a visual operation page for developers to execute SQL and provides SQL suggestions for developers in real time based on the SQL suggestion module;

[0011] The GitOps workflow module provides an integrated third-party Git project management tool to achieve the combination of database development and operation and maintenance;

[0012] The backup and recovery module provides a variety of backup mechanisms to relieve the database operation and maintenance burden on developers.

[0013] Furthermore,

[0014] The SQL audit module provides a one-stop SQL audit panel where all database change records can be visually viewed; it supports the review of SQL code and also supports the review of submitted data changes to ensure that database changes comply with established standards and rules.

[0015] The SQL audit module is based on the GitOps workflow module and uses the pull request as the trigger for the review process; the SQL statements to be audited are submitted to a specified code repository, and the system will automatically trigger the review process. The review results are presented to the user, including a detailed analysis of each SQL statement, the execution plan, and optimization suggestions;

[0016] The SQL audit module provides the management of audit process nodes, including adding and deleting audit nodes; users can add automatic audit nodes and manual audit nodes in the audit process according to actual business needs.

[0017] Among them, the automatic audit node: the automatic audit node rule uses the rule engine of the SQL suggestion module to automatically verify the developer's SQL script;

[0018] The manual audit node: the manual audit node is the user integrated in the GitOps workflow.

[0019] If any node in the SQL audit process is aborted, real-time feedback will be provided, including the display of information of its own system and the information prompt of the system integrated with the GitOps workflow module.

[0020] Furthermore,

[0021] The SQL suggestion module has a standard SQL rule engine to perform performance checks, data security checks, and database integrity checks on the SQL statements input by users, including the following:

[0022] Perform syntax checks on the SQL statements input by users to ensure that they conform to the SQL standard. If syntax errors are found, the module should provide corresponding error prompts to help users correct the problems;

[0023] Provide optimization suggestions based on the user's SQL statements. The corresponding rule engine includes the following aspects:

[0024] Security check: Ensure that the SQL statement does not contain malicious code or potential security vulnerabilities;

[0025] Performance optimization and index suggestions: The SQL suggestion module recommends creating or adjusting indexes based on the query conditions and data distribution to improve query performance;

[0026] Data integrity check: Ensure that the SQL statement does not violate data integrity constraints;

[0027] Query rewrite and complexity assessment: For complex queries, the SQL suggestion module attempts to rewrite them into a more efficient equivalent form;

[0028] Statistical information collection: The SQL suggestion module collects statistical information on database tables and indexes to more accurately evaluate query performance and provide suggestions;

[0029] Execution plan analysis: The SQL suggestion module analyzes the execution plan of the query, identifies potential performance bottlenecks, and provides corresponding optimization suggestions.

[0030] Provide real-time feedback when the user writes an SQL statement. In addition, a separate suggestion panel is provided, listing all optimization suggestions for the current SQL statement;

[0031] Save the user's SQL query history and learn and accumulate experience based on these records to provide more personalized and accurate optimization suggestions.

[0032] Furthermore,

[0033] The SQL editor module provides SQL parsing and validation, code completion tips, history, and undo / redo, import and export features;

[0034] The SQL editor module is used to write and execute SQL statements and mainly includes the following aspects:

[0035] First, the SQL editor module has a user interface. The user interface includes a text editing area for entering SQL statements, an execution button for executing the currently edited SQL statement, and a result display area for displaying query results or feedback information on other operations.

[0036] Second, it supports SQL parsing and validation; the SQL editor module can parse the SQL statements entered by the user, perform syntax checking and semantic validation, which can be achieved through the built-in SQL parser or by calling external libraries; if syntax errors or semantic problems are found, corresponding error prompts should be provided;

[0037] Thirdly, it supports code completion and hinting; the SQL editor module provides code completion function, automatically recommending possible keywords, table names, and column names according to partial content input by the user; in addition, it also provides real-time syntax hints to help users correct incorrect syntax structures;

[0038] Fourthly, it has history recording and undo / redo functions. The SQL editor module supports saving the user's history records so that users can conveniently view and modify previously executed SQL statements; at the same time, this module also provides undo and redo functions so that users can correct mistakes or restore previous changes;

[0039] Fifthly, it manages database connections. The SQL editor module supports several database connections, allowing users to switch between different databases; each connection should contain necessary connection information;

[0040] Sixthly, it provides SQL query optimization suggestions; the SQL editor module provides query optimization suggestions according to the user's SQL statements;

[0041] Seventhly, it supports export and import. The SQL editor module supports exporting SQL statements to files so that users can use them in other tools; at the same time, the editor also supports importing SQL statements from files, facilitating users to quickly create or modify existing SQL statements;

[0042] Eighthly, it has the extensibility of the SQL editor. The SQL editor module has certain extensibility, allowing users to customize functions or plugins.

[0043] Furthermore,

[0044] The GitOps workflow module supports the integration of code management tools, uses the GitOps workflow for database changes, and combines with the SQL audit module to achieve manual and automated audits of SQL;

[0045] Through the GitOps workflow module, a complete Git-based database CI / CD workflow is achieved:

[0046] (1) Developers submit the changed SQL script to the code branch;

[0047] (2) Trigger the SQL audit CI provided by the GitOps workflow module for automated SQL audit and give modification suggestions;

[0048] (3) The SQL script after the developer's modification is merged into the main branch;

[0049] (4) After the SQL script is merged into the main branch, the release process is automatically triggered, and the script will be pushed into the GitOps workflow module;

[0050] (5) The automatic review built into the GitOps workflow module will conduct a secondary confirmation on the change statements, automatically match the approval process according to the change risk level, and approve according to the approval process.

[0051] (6) The approved statements can be executed in the target library by manual or automatic triggering.

[0052] (7) The latest schema structure of the database after the change is completed will be automatically written back to the code repository.

[0053] (8) After confirming that the change is completed, trigger the application release process of the next stage.

[0054] Furthermore,

[0055] The backup and recovery module supports creating diverse backup tasks, including full backup, incremental backup, and differential backup.

[0056] The backup and recovery module supports backup storage node management to achieve local storage, local storage, and off-site storage of data, ensuring data security and integrity in terms of backup regions.

[0057] Local backup on the same machine means backing up data on the same server as the database service.

[0058] Local backup means backing up data in the same geographical location or data center as the database service system.

[0059] Off-site backup means backing up data in a different geographical location or data center from the database service system. Local backup on the same machine means backing up data on the same server as the database service.

[0060] Local backup means backing up data in the same geographical location or data center as the database service system.

[0061] Off-site backup means backing up data in a different geographical location or data center from the database service system.

[0062] The backup and recovery module supports adjusting the backup frequency and updating the backup trigger time; the backup period and specific execution time can be flexibly set through interface options according to actual business requirements.

[0063] The backup and recovery module supports viewing the backup task status and pushing exception alerts; viewing the backup task status means that system administrators and relevant responsible persons can monitor the execution status of backup tasks in real time, including whether the backup task has started, is in progress, completed, or failed; pushing exception alerts means that if any errors or abnormal situations occur during the backup process, the system will automatically generate alert messages and push them to operation and maintenance personnel or administrators.

[0064] The beneficial effects of the present invention are

[0065] 1. Improve the reliability and stability of the database;

[0066] 2. Achieve continuous integrated delivery;

[0067] 3. Enhance the reliability and stability of the system;

[0068] 4. Simplify complex backup management tasks. Specific implementation manners

[0069] To make the objectives, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below. Obviously, the described embodiments are some but not all of the embodiments of the present invention. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention.

[0070] The present invention provides a one-stop database automation management method based on the DevOps concept. This method includes a total of five core modules, namely, an SQL review module, an SQL suggestion module, an SQL editor module, a GitOps workflow module, and a backup and recovery module. These five modules cooperate with each other to jointly build a complete and efficient workflow.

[0071] The SQL review module provides a review process panel and realizes automatic SQL review and manual SQL review based on the SQL suggestion module and the GitOps workflow module. The SQL suggestion module provides an SQL suggestion rule engine for use by the SQL review module and the SQL editor module. The SQL editor module provides a visual operation page for developers to execute SQL and provides SQL suggestions for developers in real time based on the SQL suggestion module. The GitOps workflow module provides an integrated third-party Git project management tool to realize the combination of database development and operation and maintenance. The backup and recovery module provides diverse backup mechanisms to relieve the database operation and maintenance burden on developers.

[0072] The detailed functions of the above five core modules are described as follows:

[0073] (1) SQL review module

[0074] The SQL audit module has a one-stop SQL audit panel, where all database change records can be visually seen. It helps users better manage the database and ensure data security and accuracy. SQL audit supports the review of SQL code and also supports the review of submitted data changes. This function can ensure that database changes comply with established standards and rules, reducing risks caused by incorrect or insecure SQL statements.

[0075] The SQL audit module has the following characteristics:

[0076] First, it supports an automated approval process. The SQL audit module is based on the GitOps workflow module (the fourth functional module in this section), using pull requests as the trigger for the review process, which simplifies the review process. Developers only need to submit the SQL statements to be audited to the specified code repository, and the system will automatically trigger the review process. The review results will be presented to users in a clear manner, including detailed analysis of each SQL statement, execution plans, and optimization suggestions, etc. This enables users to quickly understand the quality and performance of SQL statements and optimize them accordingly.

[0077] Second, it supports configurable audit processes. The SQL audit module provides management of audit process nodes, including adding and deleting audit nodes. Users can, according to actual business needs, add automatic audit nodes and manual audit nodes to the audit process.

[0078] ● Automatic audit node: For the rules of the automatic audit node, the rule engine of the SQL suggestion module is used to automatically verify the developers' SQL scripts.

[0079] ● Manual audit node: The manual audit node is the user integrated in the GitOps workflow.

[0080] Third, it provides real-time feedback and prompts. If any node in the SQL audit process is aborted, real-time feedback will be provided, including the display of information from its own system and the information prompts from the GitOps workflow module integrated system.

[0081] (2) SQL Suggestion Module

[0082] The SQL suggestion module can automatically check the SQL statement specifications and help users optimize the performance of SQL queries. This module includes the following:

[0083] First, syntax checking and error prompts. The SQL suggestion module performs syntax checking on the SQL statements input by users to ensure they comply with SQL standards. If syntax errors are found, the module should provide corresponding error prompts to help users correct the problems.

[0084] Second is the query optimization suggestion rule engine. The core function of the SQL suggestion module is to provide optimization suggestions based on the user's SQL statements. The corresponding rule engine includes the following aspects:

[0085] ● Security check: Ensure that the SQL statement does not contain malicious code or potential security vulnerabilities.

[0086] ● Performance optimization and index suggestion: The SQL suggestion module recommends creating or adjusting indexes based on the query conditions and data distribution to improve query performance.

[0087] ● Data integrity check: Ensure that the SQL statement does not violate data integrity constraints. Such as database operations like drop, truncate, etc.

[0088] ● Query rewrite and complexity assessment: For complex queries, the SQL suggestion module attempts to rewrite them into a more efficient equivalent form, for example, using JOIN instead of Subquery.

[0089] ● Statistical information collection: The SQL suggestion module collects statistical information of database tables and indexes to more accurately evaluate query performance and provide suggestions.

[0090] ● Execution plan analysis: The SQL suggestion module analyzes the execution plan of the query, identifies potential performance bottlenecks, and provides corresponding optimization suggestions.

[0091] Third is real-time feedback and suggestion display. The SQL suggestion module provides real-time feedback when the user writes an SQL statement, such as displaying warning or prompt messages on the editor interface. In addition, the SQL suggestion module also provides a separate suggestion panel listing all optimization suggestions for the current SQL statement.

[0092] Fourth is history record and learning. The SQL suggestion module saves the user's SQL query history records and learns and accumulates experience based on these records to provide more personalized and accurate optimization suggestions.

[0093] (3) SQL Editor Module

[0094] The SQL editor module is used to write and execute SQL statements and mainly includes the following aspects:

[0095] First, the SQL editor module has a user interface. The user interface includes a text editing area for entering SQL statements, an execution button for executing the currently edited SQL statement, and a result display area for displaying query results or feedback information of other operations.

[0096] Second, it supports SQL parsing and verification. The SQL editor module can parse the SQL statements input by users and perform syntax checking and semantic verification on them. This can be achieved through a built-in SQL parser or by calling an external library. If syntax errors or semantic problems are found, the editor should provide corresponding error prompts.

[0097] Third, it supports code completion and hints. The SQL editor module provides a code completion function that automatically recommends possible keywords, table names, column names, etc. based on the partial content input by the user. In addition, the editor can also provide real-time syntax hints to help users correct incorrect syntax structures.

[0098] Fourth, it has a history record and undo / redo function. The SQL editor module supports saving the user's history record so that users can easily view and modify previously executed SQL statements. At the same time, this module also provides undo and redo functions so that users can correct mistakes or restore previous changes.

[0099] Fifth, it manages database connections. The SQL editor module supports multiple database connections, allowing users to switch between different databases. Each connection should contain necessary connection information, such as hostname, port, username, password, etc.

[0100] Sixth, it provides SQL query optimization suggestions. The SQL editor module provides some query optimization suggestions based on the user's SQL statements, such as using indexes and avoiding full table scans. These suggestions can help users improve query performance.

[0101] Seventh, it supports export and import. The SQL editor module supports exporting SQL statements to files (such as CSV, JSON, etc.) so that users can use them in other tools. At the same time, the editor also supports importing SQL statements from files, which is convenient for users to quickly create or modify existing SQL statements.

[0102] Eighth, it has the extensibility of the SQL editor. The SQL editor module has a certain degree of extensibility, allowing users to customize functions or plugins. For example, users can write specific SQL templates according to their own needs or integrate third-party tools to enhance the functions of the editor.

[0103] (4) GitOps Workflow Module

[0104] As DevOps has become mainstream, teams have begun to adopt code management tools such as GitLab / Gitea / GitHub to manage code and tools such as Terraform to manage infrastructure. Similarly, during the application development process, this management method provides a web-based workspace for DBAs and developers to collaborate and manage database changes in a secure and efficient manner.

[0105] One-stop database automation management method under the DevOps concept. The implementation of the GitOps workflow module mainly involves the integration of code management tools such as GitHub and GitLab, and uses the GitOps workflow for database changes.

[0106] Through the GitOps workflow module, we will implement a complete Git-based database CI / CD workflow:

[0107] 1. Developers submit the changed SQL scripts to the code branch;

[0108] 2. Trigger the SQL review CI provided by the GitOps workflow module for automated SQL review and give modification suggestions;

[0109] 3. The SQL scripts after the developers' modification are merged into the main branch;

[0110] 4. After the SQL scripts are merged into the main branch, the release process is automatically triggered, and the scripts will be pushed into the GitOps workflow module;

[0111] 5. The built-in automatic review in the GitOps workflow module will conduct a second confirmation on the changed statements, automatically match the approval process according to the change risk level, and approve according to the approval process;

[0112] 6. The approved statements can be executed in the target database by manual or automatic trigger;

[0113] 7. The latest schema structure of the database after the change will be automatically written back to the code repository;

[0114] 8. After confirming the completion of the change, trigger the application release process of the next stage.

[0115] (V) Backup and Recovery Module

[0116] One-stop database automation management method under the DevOps concept. The implementation of the backup and recovery module mainly involves the implementation of fully automated data backup and recovery strategies, including but not limited to the following aspects:

[0117] First, the backup and recovery module supports creating diverse backup tasks, including full backups, incremental backups, and differential backups. Although full backups are the most straightforward and simple for data recovery, incremental backups and differential backups can utilize storage space and network bandwidth more efficiently and are suitable for the needs of frequent backups.

[0118] Second, the backup and recovery module supports backup storage node management to achieve local storage, local storage, and off-site storage of data, ensuring data security and integrity in terms of backup regions. Native backup refers to the backup where the backup data and the database service are on the same server. The characteristic of this backup method is that the backup and recovery operations are very fast and not affected by network latency or bandwidth limitations. Local backup refers to the backup where the backup data and the database service system are in the same geographical location or data center. The characteristic of this backup method is that the backup speed is relatively fast, and the backup speed is usually limited by network latency or bandwidth. Off-site backup refers to the backup where the backup data and the database service system are in different geographical locations or data centers, providing higher data security. Even if the original data location (native backup, local backup) suffers from severe natural disasters or other major events, the data can still be restored from a remote location.

[0119] Third, the backup and recovery module supports adjusting the backup frequency and updating the backup trigger time. Through the white-screened page operation, the difficulty of backup management is reduced. Specifically at the operation level, users can flexibly set the backup period and specific execution time according to actual business needs through simple interface options. For example, for important systems with frequent data changes, more frequent backups can be set to reduce the risk of data loss; while for applications with less data changes, appropriately extending the backup interval can optimize the usage efficiency of storage resources.

[0120] Fourth, the backup and recovery module supports viewing the backup task status and pushing exception alerts. Viewing the backup task status means that system administrators and relevant responsible persons can monitor the execution status of backup tasks in real time, which includes but is not limited to whether the backup task has started, is in progress, completed, or failed. Exception alert pushing means that during the backup process, if any errors or abnormal situations occur, the system will automatically generate alert messages and push them to the operation and maintenance personnel or administrators.

[0121] By integrating database development and database operation and maintenance, the existing information silo situation between database development and database operation and maintenance is broken. Through automated processes, rapid, reliable, and continuous delivery of the database is achieved, while ensuring data security and integrity. This method combines the collaboration models for development and operation and maintenance teams, emphasizing the importance of communication, collaboration, integration, and automation to achieve faster and more flexible database management.

[0122] The above are only the preferred embodiments of the present invention, which are only used to illustrate the technical solutions of the present invention and are not used to limit the protection scope of the present invention. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principle of the present invention are included in the protection scope of the present invention.

Claims

1. A one-stop database automation management system based on the DevOps concept, characterized in that: include: SQL audit module, which provides audit process panel and implements SQL automatic audit and manual SQL audit based on SQL suggestion module and GitOps workflow module; SQL suggestion module, which provides SQL suggestion rule engine for use by SQL audit module and SQL editor module; The SQL editor module provides a visual operation page for developers to execute SQL and provides SQL suggestions to developers in real time based on the SQL suggestion module; The GitOps workflow module provides integration of third-party Git project management tools to achieve the combination of database development and operation and maintenance; The backup and recovery module provides a variety of backup mechanisms to reduce the database operation and maintenance burden for developers.

2. The system according to claim 1, characterized in that The SQL Audit module provides a one-stop SQL audit panel, which allows you to intuitively view all database change records; it supports the review of SQL codes and the review of submitted data changes to ensure that database changes comply with established standards and rules.

3. The system according to claim 2, characterized in that The SQL review module is based on the GitOps workflow module and uses pull request as the review process trigger. When the SQL statement to be reviewed is submitted to the specified code library, the system will automatically trigger the review process and present the review results to the user, including detailed analysis, execution plan and optimization suggestions for each SQL statement. The SQL audit module provides management of audit process nodes, including adding audit nodes and deleting audit nodes. Users can add automatic audit nodes and manual audit nodes to the audit process according to actual business needs. Among them, automatic audit node: automatic audit node rules, using the SQL suggestion module rule engine to automatically verify the developer's SQL script; Manual review node: The manual review node is a user integrated in the GitOps workflow; If any node in the SQL audit process is terminated, real-time feedback will be provided, including information display of its own system and information prompts of the GitOps workflow module integrated system.

4. The system according to claim 1, characterized in that The SQL suggestion module has a standard SQL rule engine that performs performance checks, data security checks, and database integrity checks on SQL statements entered by users, including the following: Perform syntax check on SQL statements entered by users to ensure that they comply with SQL standards. If syntax errors are found, the module should provide corresponding error prompts to help users correct the problems. Provide optimization suggestions based on the user's SQL statements. The corresponding rule engine includes the following aspects: Security check: Ensure that SQL statements do not contain malicious code or potential security vulnerabilities; Performance optimization and index suggestions: The SQL suggestion module recommends creating or adjusting indexes to improve query performance based on query conditions and data distribution; Data integrity check: ensure that SQL statements do not violate data integrity constraints; Query rewriting and complexity assessment: For complex queries, the SQL suggestion module attempts to rewrite them into a more efficient equivalent form; Statistics collection: The SQL suggestion module collects statistics of database tables and indexes to more accurately evaluate query performance and provide suggestions; Execution plan analysis: The SQL suggestion module analyzes the query execution plan, identifies potential performance bottlenecks, and provides corresponding optimization suggestions; Provides real-time feedback when users write SQL statements, and also provides a separate suggestion panel that lists all optimization suggestions for the current SQL statement; Save the user's SQL query history, and learn and accumulate experience based on these records to provide more personalized and accurate optimization suggestions.

5. The system according to claim 1, characterized in that SQL Editor module, which provides SQL parsing and verification, code completion prompts, history and undo / redo, import and export features; The SQL Editor module is used to write and execute SQL statements, mainly including the following aspects: First, the SQL editor module has a user interface, which includes a text editing area for inputting SQL statements; an execution button for executing the currently edited SQL statement; and a result display area for displaying query results or other operation feedback information; Second, it supports SQL parsing and verification; the SQL editor module parses the SQL statements entered by the user and performs syntax checking and semantic verification on them, which is achieved through the built-in SQL parser or calling external libraries; If grammatical errors or semantic problems are found, corresponding error prompts are provided; The third is to support code completion and prompts. The SQL editor module provides code completion function, which automatically recommends possible keywords, table names, and column names based on the partial content entered by the user. In addition, it also provides real-time syntax prompts to help users correct incorrect syntax structures. Fourth, history and undo / redo. The SQL Editor module supports saving the user's history so that you can view and modify previously executed SQL statements. At the same time, the module also provides undo and redo functions so that users can correct errors or restore previous changes. Fifth, database connection management. The SQL editor module supports several database connections, allowing users to switch between different databases; each connection should contain the necessary connection information; Sixth, SQL query optimization suggestions; SQL Editor Module The editor provides query optimization suggestions based on the user's SQL statements; Seventh, export and import; the SQL editor module supports exporting SQL statements as files so that users can use them in other tools; at the same time, the editor also supports importing SQL statements from files, making it convenient for users to quickly create or modify existing SQL statements; Eighth, the SQL editor is extensible; the SQL editor module is extensible, allowing users to customize functions or plug-ins.

6. The system according to claim 1, characterized in that The GitOps workflow module supports the integration of code management tools, uses GitOps workflow to make database changes, and combines it with the SQL audit module to implement manual and automated SQL audits; Through the GitOps workflow module, a complete Git-based database CI / CD workflow is implemented, including: (1) The developer submits the changed SQL script to the code branch; (2) Trigger the SQL audit CI provided by the GitOps workflow module to perform automated SQL audits and provide modification suggestions; (3) The developer merges the modified SQL script into the main branch; (4) After the SQL script is merged into the main branch, the release process is automatically triggered and the script will be pushed to the GitOps workflow module; (5) The built-in automatic review of the GitOps workflow module will double-confirm the change statement, automatically match the approval flow according to the change risk level, and approve it according to the approval flow; (6) The approved statements can be executed in the target database through manual or automatic triggering; (7) After the change is completed, the latest database schema structure will be automatically written back to the code repository; (8) After confirming that the changes are complete, the next stage of the application release process is triggered.

7. The system according to claim 1, characterized in that The backup and recovery module supports the creation of various backup tasks, including full backup, incremental backup, and differential backup; The backup and recovery module supports backup storage node management to achieve local storage, local storage, and remote storage of data, ensuring data security and integrity in the backup region; The backup and recovery module supports backup frequency adjustment and updates the backup trigger time. The backup cycle and specific execution time can be flexibly set according to actual business needs through interface options. The backup and recovery module supports backup task status viewing and abnormal alarm push; Backup task status viewing is the ability to monitor the execution of backup tasks in real time, including whether the backup task is started, in progress, completed or failed; abnormal alarm push means that if any errors or abnormal situations are encountered during the backup process, the system will automatically generate and push alarm information.

8. The system according to claim 7, characterized in that Local backup refers to backups where the backup data and database service are on the same server; Local backup refers to backups that are performed in the same geographical location or data center as the database service system; Offsite backup refers to backup performed in a different geographical location or data center than the backup data and the database service system.