CN110968569B - Database management method, database management device, and storage medium - Google Patents

Abstract

The invention discloses a database management method, which includes the following steps: after detecting that the database operation audit initiated based on the data definition language is completed, obtaining the database targeted by the database operation as the first database; changing the database operation according to the database operation. The first database is used to obtain a second database; and the second database is updated to the latest version of the database. The invention also discloses a database management device and a computer-readable storage medium. The invention improves the efficiency of database management.

Description

Database management method, database management device and storage medium

Technical field

The present invention relates to the field of database technology, and in particular, to a database management method, a database management device and a computer-readable storage medium.

Background technique

In an actual production environment, due to the large number of databases, the risk of DDL (Data Definition Language) changes is high. Therefore, in order to effectively manage DDL, approval and execution scenarios are generally added to the database management system for production business. process. However, in existing database management, there are problems such as high approval costs and slow processes, resulting in low efficiency of database management.

The above content is only used to assist in understanding the technical solution of the present invention, and does not represent an admission that the above content is prior art.

Contents of the invention

The main purpose of the present invention is to provide a database management method, a database management device and a computer-readable storage medium, so as to improve the efficiency of database management.

In order to achieve the above object, the present invention provides a database management method. The database management method includes the following steps:

After detecting that the database operation review initiated based on the data definition language is completed, obtain the database targeted by the database operation as the first database;

Modify the first database according to the database operation to obtain a second database;

The second database is updated to the latest version of the database.

Optionally, after the step of changing the first database according to the database operation to obtain the second database, the method further includes:

Detect whether the second database meets preset requirements;

When the second database meets the preset requirements, the step of updating the second database to the latest version of the database is performed.

Optionally, after the step of detecting whether the second database meets preset requirements, the step further includes:

When the second database does not meet the preset requirements, the second database is restored to the first database.

Optionally, the step of detecting whether the second database meets preset requirements includes:

Output the second database to the associated terminal of the tester, so that the tester can detect whether the second database meets the preset requirements;

Upon receiving the confirmation response sent by the associated terminal, it is determined that the second database meets the preset requirements;

When receiving the cancellation response sent by the associated terminal, it is determined that the second database does not meet the preset requirements.

Optionally, after the step of detecting whether the second database meets preset requirements, the step further includes:

When the second database does not meet the preset requirements and when the data definition language data packet sent by the associated terminal is received, update the second database according to the data definition language data packet to obtain a third database;

The third database is updated to the latest version of the database.

Optionally, after the step of changing the first database according to the database operation to obtain the second database, the method further includes:

When the latest version of the database is generated, save the previous version of the database and record the save time;

When receiving the database version change instruction, obtain from the saved database the database corresponding to the storage time and the time targeted by the database version change instruction;

Update the obtained database to the latest version.

Optionally, after the step of changing the first database according to the database operation to obtain the second database, the method further includes:

When the latest version of the database is generated, the previous version of the database is saved;

Provide the saved database in the database version selection interface;

When a database selection instruction generated based on the database version selection interface is detected, the database targeted by the database selection instruction is loaded.

In order to achieve the above object, the present invention also provides a database management device. The database management device includes:

The database management device includes a memory, a processor, and a database management program stored in the memory and executable on the processor. When the database management program is executed by the processor, the above database is implemented. management steps.

In order to achieve the above object, the present invention also provides a computer-readable storage medium. The computer-readable storage medium stores a database management program. When the database management program is executed by the processor, the above-mentioned database management method is implemented. A step of.

The database management method, database management device and computer-readable storage medium provided by the present invention, after detecting that the database operation review initiated based on the data definition language is completed, obtains the database targeted by the database operation as the first database; according to the The database operation changes the first database to obtain a second database; and updates the second database to the latest version of the database. In this way, the efficiency of database management is improved.

Description of the drawings

Figure 1 is a schematic diagram of the hardware operating environment of the embodiment terminal involved in the embodiment of the present invention;

Figure 2 is a schematic flow chart of the first embodiment of the database management method of the present invention;

Figure 3 is a schematic flow chart of the second embodiment of the database management method of the present invention;

Figure 4 is a schematic flowchart of a third embodiment of the database management method of the present invention.

The realization of the purpose, functional features and advantages of the present invention will be further described with reference to the embodiments and the accompanying drawings.

Detailed ways

It should be understood that the specific embodiments described here are only used to explain the present invention and are not intended to limit the present invention.

The invention provides a database management method, which improves the efficiency of database management.

As shown in Figure 1, Figure 1 is a schematic diagram of the hardware operating environment of the embodiment terminal involved in the embodiment of the present invention;

The terminal in the embodiment of the present invention may be a database management device or a database management system.

As shown in Figure 1, the terminal may include: a processor 1001, such as a CPU central processing unit (central processing unit), a memory 1002, and a communication bus 1003. Among them, the communication bus 1003 is used to realize connection and communication between various components in the terminal. The memory 1002 may be a high-speed RAM random-access memory (random-access memory) or a stable memory (non-volatile memory), such as a disk memory. The memory 1002 may optionally be a storage device independent of the aforementioned processor 1001.

Those skilled in the art can understand that the structure of the terminal shown in Figure 1 does not constitute a limitation on the terminal according to the embodiment of the present invention. It may include more or fewer components than shown in the figure, or some components may be combined, or different components may be used. layout.

As shown in FIG. 1 , a memory 1002 as a computer storage medium may include a database management program.

In the terminal shown in Figure 1, the processor 1001 can be used to call the management program of the database stored in the memory 1002, and perform the following operations:

After detecting that the database operation review initiated based on the data definition language is completed, obtain the database targeted by the database operation as the first database;

Modify the first database according to the database operation to obtain a second database;

The second database is updated to the latest version of the database.

Further, the processor 1001 can call the management program of the database stored in the memory 1002, and also perform the following operations:

Detect whether the second database meets preset requirements;

When the second database meets the preset requirements, the step of updating the second database to the latest version of the database is performed.

Further, the processor 1001 can call the management program of the database stored in the memory 1002, and also perform the following operations:

When the second database does not meet the preset requirements, the second database is restored to the first database.

Further, the processor 1001 can call the management program of the database stored in the memory 1002, and also perform the following operations:

Output the second database to the associated terminal of the tester, so that the tester can detect whether the second database meets the preset requirements;

Upon receiving the confirmation response sent by the associated terminal, it is determined that the second database meets the preset requirements;

When receiving the cancellation response sent by the associated terminal, it is determined that the second database does not meet the preset requirements.

Further, the processor 1001 can call the management program of the database stored in the memory 1002, and also perform the following operations:

When the second database does not meet the preset requirements and when the data definition language data packet sent by the associated terminal is received, update the second database according to the data definition language data packet to obtain a third database;

The third database is updated to the latest version of the database.

Further, the processor 1001 can call the management program of the database stored in the memory 1002, and also perform the following operations:

When the latest version of the database is generated, save the previous version of the database and record the save time;

When receiving the database version change instruction, obtain from the saved database the database corresponding to the storage time and the time targeted by the database version change instruction;

Update the obtained database to the latest version.

Further, the processor 1001 can call the management program of the database stored in the memory 1002, and also perform the following operations:

When the latest version of the database is generated, the previous version of the database is saved;

Provide the saved database in the database version selection interface;

When a database selection instruction generated based on the database version selection interface is detected, the database targeted by the database selection instruction is loaded.

Referring to Figure 2, in one embodiment, the database management method includes:

Step S10: After detecting that the database operation audit initiated based on the data definition language is completed, obtain the database targeted by the database operation as the first database.

Step S20: Modify the first database according to the database operation to obtain a second database.

In this embodiment, the embodiment terminal may be a database management device or a database management system. The following description takes the embodiment in which the terminal is a database management device as an example.

Structured Query Language (SQL), referred to as SQL, is a special-purpose programming language. It is a database query and programming language used to access data and query, update and manage relational database systems. SQL is a standard language used to perform data operations, retrieval and maintenance on relational databases. It can be used to query data, manipulate data, define data, and control data. All databases use the same or similar language. Among them, DDL data definition language (also known as database schema definition language) is a component of the SQL language and defines the table structure of the database.

Optionally, when database developers submit DDL change requirements, they can create corresponding database operations based on data definition language, and submit the created database operations to the company manager or DBA database administrator (Database Administrator) for approval. Among them, DDL change requirements include creating databases, creating database tables, modifying database tables, deleting database tables, and deleting data table contents.

Optionally, the database administrator's approval terminal is associated with the terminal. When the database administrator believes that there is no problem with the database operation, a notification of completion of the database operation review can be sent to the terminal through the approval terminal. After receiving the notification that the database operation review is completed, the terminal determines that the database operation review is completed. This speeds up the approval process for database operations.

Optionally, after detecting that the database operation audit initiated based on the data definition language is completed, the terminal acquires all databases targeted by the database operation as the first database in the database system. And extract DDL statements from the Schema information of the database operation, and use the DDL statements to perform operations such as addition, deletion, modification, and deletion of the first database, thereby changing the first database to the second database. Among them, when the database operation targets multiple databases, the terminal searches for all databases that need to be automatically changed from the database system and makes changes. In this way, the terminal automatically executes DDL statements after the database operation is audited, without manual intervention.

In this way, DDL that has been audited by the production system is automatically executed, preventing non-standard DDL from being executed at will, and avoiding the need for rollback of changes in the pre-generated database (ie, the second database).

Step S30: Update the second database to the latest version of the database.

Optionally, the testers of the company or unit can pre-design the preset requirements of the database according to the company or unit's usage requirements for the database, and upload the preset requirements to the terminal. The preset requirements define the table format, table structure, types of sensitive data that cannot be deleted, sensitive data that cannot be deleted, etc.

Optionally, after the second database is generated, the terminal compares the second database with the preset requirements, checks whether the second database meets the preset requirements, and checks that the table format, table structure and other contents of the second database are all correct. When the preset requirements are met, the second database is released to the database production system to update the second database to the latest version of the database, that is, the second database is used as the database for actual application.

Optionally, if the terminal detects that the second database does not meet the preset requirements, it may restore the second database to the first database and retain the current version of the database. At this time, the developer needs to go through the process again and resubmit a new DDL change application.

In this way, the efficiency of database management is improved by realizing intelligent auditing generated by the database.

Optionally, the terminal may also be an associated terminal associated with a tester. After the second database is generated, the terminal sends the second database to the associated terminal for the tester to detect whether the second database meets the preset requirements. Optionally, when the tester detects that the second database meets the preset requirements, the tester can send a confirmation response of the second database to the terminal through the associated terminal. After receiving the confirmation response of the second database, the terminal determines that the second database meets the preset requirements. Set up requirements and publish the second database to the database production system to update the second database to the latest version of the database.

Optionally, when the tester detects that the second database does not meet the preset requirements, the tester can send a cancellation response of the second database to the terminal through the associated terminal. When the terminal receives the cancellation response of the second database, it determines that the second database The database does not meet the preset requirements and the second database is restored to the first database and the current version of the database is retained.

Optionally, when the tester detects that the second database does not meet the preset requirements, the tester can modify the DDL statement corresponding to the database operation, create a data definition language data package based on the modified DDL statement, and then send the data to the terminal through the associated terminal. Send the data definition language packet of the second database. After receiving the data definition language packet, the terminal determines that the second database does not meet the preset requirements and extracts the DDL statement in the data definition language packet based on the extracted DDL statement. Making changes to the second database, that is, overwriting, modifying, or deleting errors in the second database, to modify the second database into a third database. The third database is then published to the database production system to update the third database to the latest version of the database.

In this way, the process approval costs caused by the separation of the change process between the pre-generated database and the actual application database can be reduced.

Among them, before the associated terminal sends the data definition language data packet (i.e., DDL data packet) to the terminal, the audit node of the data definition language data packet can be submitted to the test DBA for approval by the test DBA. After the test DBA confirms the data definition language After there is no problem with the data packet, a confirmation response of the data definition language data packet is sent to the associated terminal. At this time, the associated terminal then sends the data definition language data packet to the terminal. In this way, by providing approval control for non-standard DDL, DDL modification or rollback scenarios that inevitably occur during the testing process are covered.

In one embodiment, after it is detected that the audit of the database operation initiated based on the data definition language is completed, the database targeted by the database operation is obtained as the first database; the first database is modified according to the database operation to obtain the second database ;Update the second database to the latest version of the database. In this way, the efficiency of database management is improved.

In the second embodiment, as shown in Figure 3, based on the above embodiment shown in Figure 2, after the step of changing the first database according to the database operation to obtain the second database, it also includes :

Step S40: When the latest version of the database is generated, save the previous version of the database and record the saving time.

Step S41: When receiving the database version change instruction, obtain the database corresponding to the storage time and the time targeted by the database version change instruction from the saved database.

Step S42: Update the obtained database to the latest version of the database.

In this embodiment, whenever the terminal detects that a database with the latest version is generated, it saves the database of the latest version and the previous version in a normalized DDL manner, and at the same time records the storage time of the saved database. When the tester believes that there is a need to restore the current application database to an old version of the database, the tester can send a database version change instruction to the terminal through the associated terminal. Among them, a set time is set in the database version change command. When the terminal receives the database version change command, it queries the databases of each version saved before the set time to obtain the database with the latest save time (that is, the database of these versions). In the database, the database with the latest save time is used as the database corresponding to the time targeted by the database version change instruction), and the obtained database is updated to the latest version of the database, that is, the currently obtained database is used as the database for actual application.

In this way, testers can roll back to the DDL version at a specified time at any time, reducing the cumbersome work of manually writing SQL statements to roll back changes to the database.

In the third embodiment, as shown in Figure 4, based on the above-mentioned embodiments of Figures 2 to 3, after the step of changing the first database according to the database operation to obtain the second database, it also includes :

Step S50: When the latest version of the database is generated, save the previous version of the database.

Step S51: Provide the saved database on the database version selection interface.

Step S52: When detecting a database selection instruction generated based on the database version selection interface, load the database targeted by the database selection instruction.

In this embodiment, whenever the terminal detects that a database with the latest version is generated, the latest version of the database of the previous version is stored in normalized DDL.

Optionally, the terminal is provided with a database version selection interface, and the database version selection interface is displayed through a display device connected to the terminal. Among them, the database version selection interface displays all versions of the database saved by the terminal. The user can perform a database selection operation based on the database version selection interface (for example, using the cursor to click on the database to be selected). When the terminal detects the user's selection operation, it generates a database selection instruction based on the database selected by the selection operation.

Optionally, when it is detected that the database selection instruction is generated, the database targeted by the database selection instruction is loaded and loaded as the database of the current application.

In this way, the specified version of the DDL database can be quickly deployed, and the parallel development work of different versions of the database for the same application can be better supported.

In addition, the present invention also proposes a database management device. The database management device includes a memory, a processor, and a database management program stored in the memory and executable on the processor. The processor executes the database The management program is the step of implementing the database management method described in the above embodiment.

In addition, the present invention also proposes a computer-readable storage medium. The computer-readable storage medium includes a database management program. When the database management program is executed by a processor, the database management method as described in the above embodiments is implemented. A step of.

The above serial numbers of the embodiments of the present invention are only for description and do not represent the advantages and disadvantages of the embodiments.

Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus the necessary general hardware platform. Of course, it can also be implemented by hardware, but in many cases the former is optional. implementation. Based on this understanding, the technical solution of the present invention can be embodied in the form of a software product that is essentially or contributes to the existing technology. The computer software product is stored in a storage medium (such as ROM/RAM) as mentioned above. , magnetic disk, optical disk), including several instructions to cause a terminal device (which can be a television, a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in various embodiments of the present invention.

The above are only optional embodiments of the present invention, and do not limit the patent scope of the present invention. Any equivalent structure or equivalent process transformation made by using the description and drawings of the present invention, or directly or indirectly applied to other related technologies fields are equally included in the scope of patent protection of the present invention.

Claims (7)

1. A method of managing a database, the method comprising the steps of:

receiving DDL change requirements, and creating corresponding database operations based on a data definition language, wherein the DDL change requirements comprise creating a database, creating a database table, modifying the database table, deleting the database table and deleting the contents of the database table;

after detecting that the database operation audit initiated based on the data definition language is completed, acquiring a database aimed at by the database operation as a first database;

changing the first database according to the database operation to obtain a second database;

outputting the second database to an associated terminal of a tester so that the tester can detect whether the second database meets a preset requirement, wherein the preset requirement is defined by a table format, a table structure, a type of undeletable sensitive data and undeletable sensitive data of the database;

when a confirmation response sent by the association terminal is received, judging that the second database meets preset requirements;

when a cancellation response sent by the associated terminal is received, judging that the second database does not meet preset requirements;

when the second database does not meet the preset requirement and when a data definition language data packet sent by the associated terminal is received, DDL sentences in the data definition language data packet are extracted, and the second database is changed based on the extracted DDL sentences to obtain a third database;

and updating the third database to the latest version database.

2. The method for managing databases according to claim 1, wherein after the step of detecting whether the second database meets a preset requirement, further comprising:

and when the second database meets the preset requirement, executing the step of updating the second database into the latest version database.

3. The method for managing databases according to claim 2, wherein after the step of detecting whether the second database meets a preset requirement, further comprising:

and when the second database does not meet the preset requirement, restoring the second database into the first database.

4. The method for managing databases according to claim 1 or 2, characterized in that after the step of modifying the first database according to the database operation to obtain a second database, further comprising:

when the database of the latest version is generated, the database of the previous version is stored, and the storage time is recorded;

when a database version change instruction is received, acquiring a database corresponding to the time for which the database version change instruction aims from a stored database;

and updating the acquired database into the latest version database.

5. The method for managing databases according to claim 1 or 2, characterized in that after the step of modifying the first database according to the database operation to obtain a second database, further comprising:

when the database of the latest version is generated, the database of the previous version is stored;

providing a stored database in a database version selection interface;

and loading the database aimed at by the database selection instruction when the database selection instruction generated based on the database version selection interface is detected.

6. A database management device, characterized in that the database management device comprises a memory, a processor and a database management program stored on the memory and executable on the processor, the database management program implementing the steps of the database management method according to any one of claims 1 to 5 when being executed by the processor.

7. A computer-readable storage medium, wherein a management program of a database is stored on the computer-readable storage medium, which when executed by a processor, implements the steps of the method for managing a database according to any one of claims 1 to 5.