CN116662297A

CN116662297A - One-stop database work order management method and platform

Info

Publication number: CN116662297A
Application number: CN202310567899.4A
Authority: CN
Inventors: 糜清照
Original assignee: Shanghai Zhongtongji Network Technology Co Ltd
Current assignee: Shanghai Zhongtongji Network Technology Co Ltd
Priority date: 2023-05-18
Filing date: 2023-05-18
Publication date: 2023-08-29

Abstract

The application relates to the technical field of database work order management, in particular to a one-stop database work order management method and a platform, wherein the method comprises the following steps: receiving a work order application initiated by a user; the work order application is generated according to the database catalogue under the product; providing a preset work order template for a user; the work order template comprises a preset SQL writing prompt; receiving a work order submitted by a user, judging the type of the work order, and executing a corresponding approval process according to the type of the work order; executing the work order after the work order approval passes, and monitoring and displaying the execution progress of the work order. In the technical scheme of the application, the work order application initiated by the user is generated according to the database catalog under the product, and the user does not need to manually input the database information. And the work order template provided for the user contains a preset SQL writing prompt, so that the workload of the user for filling the work order is reduced, and the management and maintenance of operation and maintenance personnel are facilitated.

Description

One-stop database work order management method and platform

Technical Field

The application relates to the technical field of database work management, in particular to a one-stop database work management method and a platform.

Background

With the expansion of the service, the types of databases required to be used by different types of service are increased, the change specifications of the databases of different types are different, and the operation and maintenance cost is greatly increased by only checking the worksheet manually, so that the working efficiency of development and operation and maintenance personnel is reduced.

In the prior art, different types of database worksheets are submitted, developers need to manually input database information in the worksheets, and the input information is more and the efficiency is low. Different types of database worksheets submit, developers also need to write SQL (structured query language ), and various rules need to be satisfied, which increases the workload and is inconvenient to manage and maintain.

Disclosure of Invention

The application provides a one-stop database work order management method and platform, which aims to overcome the problems of more input information, low efficiency, large workload and inconvenience in management and maintenance in the related technology at least to a certain extent.

The scheme of the application is as follows:

according to a first aspect of an embodiment of the present application, there is provided a one-stop database job management method, including:

receiving a work order application initiated by a user; the work order application is generated according to a database catalog under the product;

providing a preset work order template for a user; the work order template comprises a preset SQL writing prompt;

receiving a work order submitted by a user, judging the type of the work order, and executing a corresponding approval process according to the type of the work order;

executing the work order after the work order approval passes, and monitoring and displaying the execution progress of the work order.

Preferably, the method further comprises:

and uniformly managing the data sources of all the databases accessed by the platform, automatically synchronizing the databases to corresponding products after the database is established, and generating database catalogues under the corresponding products.

Preferably, after receiving the work order submitted by the user, the method further comprises:

judging whether the SQL line number in the work order submitted by the user exceeds a preset line number or not;

if the number exceeds the preset line number, filtering the work orders submitted by the user, and then monitoring the non-compliance items;

if the number of the work orders does not exceed the preset line number, directly monitoring the non-compliance items in the work orders submitted by the users;

and generating a modification prompt for the non-compliance items in the worksheet submitted by the user, and feeding back to the user.

Preferably, executing the corresponding approval process according to the work order type includes:

determining the influence range of the work order type;

if the influence range of the work order type does not exceed the preset range threshold value, executing a first-level approval process;

if the influence range of the work order type exceeds a preset range threshold value, executing a second-level approval process;

the approval level of the second-level approval process is higher than that of the first-level approval process.

Preferably, executing the work order includes:

if the type of the work order is DDL work order, when the current node fails to execute in the work order executing process, skipping the current node to continue executing or skipping SQL which is successfully executed to continue executing;

and if the type of the work order is a DML work order, stopping executing the work order when the current node fails to execute in the work order executing process.

Preferably, executing the work order further comprises:

and executing the work order according to the work order execution time set by the user.

Preferably, monitoring and displaying the work order execution progress includes:

determining the type of a database corresponding to the work order;

and if the database corresponding to the work order is a database of the sub-database sub-table, concurrently monitoring the execution progress of the work order.

Preferably, the method further comprises:

and recording the execution process and the execution result of the work order.

According to a second aspect of an embodiment of the present application, there is provided a one-stop database job management platform, including:

a processor and a memory;

the processor is connected with the memory through a communication bus:

the processor is used for calling and executing the program stored in the memory;

the memory is used for storing a program at least for a one-stop database job management method as described in any one of the above.

The technical scheme provided by the application can comprise the following beneficial effects: a station type database work order management method comprises the following steps: receiving a work order application initiated by a user; the work order application is generated according to the database catalogue under the product; providing a preset work order template for a user; the work order template comprises a preset SQL writing prompt; receiving a work order submitted by a user, judging the type of the work order, and executing a corresponding approval process according to the type of the work order; executing the work order after the work order approval passes, and monitoring and displaying the execution progress of the work order. In the technical scheme of the application, the work order application initiated by the user is generated according to the database catalog under the product, and the user does not need to manually input the database information. And the work order template provided for the user contains a preset SQL writing prompt, so that the workload of the user for filling the work order is reduced, and the management and maintenance of operation and maintenance personnel are facilitated.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application as claimed.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application.

FIG. 1 is a schematic flow chart of a method for managing a workstation in a database according to an embodiment of the present application;

FIG. 2 is a schematic block diagram of a one-stop database job management platform provided by one embodiment of the present application.

Reference numerals: a processor-21; and a memory 22.

Detailed Description

Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the application. Rather, they are merely examples of apparatus and methods consistent with aspects of the application as detailed in the accompanying claims.

Example 1

Fig. 1 is a schematic flow chart of a one-station database job management method according to an embodiment of the present application, referring to fig. 1, a one-station database job management method includes:

s11: receiving a work order application initiated by a user; the work order application is generated according to the database catalogue under the product;

s12: providing a preset work order template for a user; the work order template comprises a preset SQL writing prompt;

s13: receiving a work order submitted by a user, judging the type of the work order, and executing a corresponding approval process according to the type of the work order;

s14: executing the work order after the work order approval passes, and monitoring and displaying the execution progress of the work order.

It should be noted that, the technical scheme in this embodiment relates to the technical field of database work management, and in particular to a one-stop database work management method.

It should be noted that the method further includes:

The platform in the embodiment is a one-stop database work order management platform, is a one-stop management platform, integrates various pt tools and various components including the goingdegree at the bottom layer, and can simultaneously support the work order auditing and submitting functions of various main flow databases such as Oracle, mySQL, TIDB.

It should be noted that, the platform in this embodiment adopts a master-slave architecture, and the master architecture is used for maintaining the meta information of the cluster, and further performs scheduling by means of the meta information. The slave architecture is responsible for reading and writing specific data slices (storage systems) or as execution units for sub-tasks (computing systems).

It should be noted that, in this embodiment, the data sources of all the databases accessed by the platform are managed in a unified manner, and the databases are automatically synchronized to the corresponding products after the database is created, and the database catalogue is generated under the corresponding products, so that the developer with the development authority of the products can see the databases corresponding to the products. The user initiates the work order application, and only clicks the application work order in the corresponding database catalog under the product.

In this embodiment, the developer is the user.

It should be noted that, in the embodiment, the work order template includes a preset SQL writing prompt, and for a DDL (data definition language ) work order, a developer only needs to fill in a field name, a data type, an annotation and a table name. The operation and maintenance personnel can manage and maintain conveniently.

It should be noted that, after receiving the work order submitted by the user, the method further includes:

It can be understood that in this embodiment, SQL verification is performed after receiving a work order submitted by a user, and if the number of lines is relatively large, filtering is supported to check out non-compliance items.

It should be noted that, in this embodiment, the download viewing is also supported when the SQL verification is performed.

It should be noted that, executing the corresponding approval process according to the worksheet type includes:

determining the influence range of the work order type;

wherein, the approval level of the second-level approval process is higher than that of the first-level approval process.

By way of example, the work order types include work order types with a small scope of influence, such as DDL work order and DML (data processing language, data Manipulation Language) work order, and also include work order types with a large scope of influence.

If the work order type is DDL work order/DML work order, the first-level approval process comprises the following steps:

judging whether to skip a product responsible person;

if the person in charge of the product is not skipped, the person in charge of the product, the person in charge of development and the direct leader carry out step-by-step approval; in the approval process, whether the development responsible person is a work order applicant or not needs to be confirmed;

if the product responsible person is skipped, the development responsible person and the generic leader conduct step-by-step approval; in the approval process, whether the development responsible person has the work order applicant or not needs to be confirmed.

If the development responsible person is not the work order applicant, the process is directly ended.

If the influence range of the work order type exceeds the preset range threshold, executing a second-level approval process comprises the following steps:

judging whether development responsible persons exist or not;

if a development responsible person exists, performing the approval of the development responsible person, the security approval and the approval of DBA (database manager, database Administrator) step by step;

if no development responsible person exists, the development direct lead approval, the safety approval and the DBA approval are carried out step by step.

It should be noted that, whether the first level approval process or the second level approval process, any one of the auditing nodes in the approval process does not pass the approval, and the work order needs to be returned to the developer or the last auditing node.

In this embodiment, for the work order type with a larger influence range, the work order type is approved by the DBA, and the feasibility, safety and integrity of the work order are ensured through the DBA approval.

The execution of the work order includes:

In the execution process of the work order, the background monitors the execution state of the work order in real time, the failure of the DDL work order part node does not cause the whole work order to stop executing, and the work order of the DML is not continued once the failure occurs.

In addition, the job ticket execution failure may be caused by various reasons such as network, and in this embodiment, when the DDL job ticket execution fails, the current node continues to execute, and also supports the SQL continuing execution that skips execution success.

It should be noted that, in this embodiment, the execution failure SQL may be fast located according to the failure status, and the download viewing is supported.

It should be noted that executing the work order further includes:

The work order supports timing execution, and the timing execution is supported in any low-peak period of the service.

Preferably, the work order supports the mobile terminal, the authorized development and execution, and supports the self-timing execution of the developer.

It should be noted that, monitoring and displaying the execution progress of the work order includes:

determining the type of a database corresponding to the work order;

It can be understood that the existing work order system does not support the submission of SQL work orders of the type of the database and the table, and a developer needs to calculate the database table into which the data falls to perform query modification. In this embodiment, when the database corresponding to the work order is a database of a database division and a table division, the execution progress of the work order is monitored concurrently, the database division and table division query is supported, the DML is changed, and the SQL is automatically distributed to the corresponding database table, so that a developer does not need to manually query the split data to waste time.

It should be noted that, the execution progress of the work order is displayed, and the developer can check the execution progress bar of the work order in real time.

The method further comprises the steps of:

and recording the execution process and the execution result of the work order.

It can be understood that in this embodiment, by recording the execution process and the execution result of the work order, and recording the change log in detail, the related user can be queried and located, so that the audit security is ensured.

Example two

FIG. 2 is a schematic block diagram of a one-stop database job management platform according to one embodiment of the present application, and referring to FIG. 2, a one-stop database job management platform includes:

a processor 21 and a memory 22;

the processor 21 is connected to the memory 22 via a communication bus:

wherein the processor 21 is used for calling and executing the program stored in the memory 22;

the memory 22 is used for storing a program for executing at least the one-stop database job management method in the above embodiment.

It is to be understood that the same or similar parts in the above embodiments may be referred to each other, and that in some embodiments, the same or similar parts in other embodiments may be referred to.

It should be noted that in the description of the present application, the terms "first," "second," and the like are used for descriptive purposes only and are not to be construed as indicating or implying relative importance. Furthermore, in the description of the present application, unless otherwise indicated, the meaning of "plurality" means at least two.

Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process, and further implementations are included within the scope of the preferred embodiment of the present application in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the present application.

It is to be understood that portions of the present application may be implemented in hardware, software, firmware, or a combination thereof. In the above-described embodiments, the various steps or methods may be implemented in software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, may be implemented using any one or combination of the following techniques, as is well known in the art: discrete logic circuits having logic gates for implementing logic functions on data signals, application specific integrated circuits having suitable combinational logic gates, programmable Gate Arrays (PGAs), field Programmable Gate Arrays (FPGAs), and the like.

Those of ordinary skill in the art will appreciate that all or a portion of the steps carried out in the method of the above-described embodiments may be implemented by a program to instruct related hardware, where the program may be stored in a computer readable storage medium, and where the program, when executed, includes one or a combination of the steps of the method embodiments.

In addition, each functional unit in the embodiments of the present application may be integrated in one processing module, or each unit may exist alone physically, or two or more units may be integrated in one module. The integrated modules may be implemented in hardware or in software functional modules. The integrated modules may also be stored in a computer readable storage medium if implemented in the form of software functional modules and sold or used as a stand-alone product.

The above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, or the like.

In the description of the present specification, a description referring to terms "one embodiment," "some embodiments," "examples," "specific examples," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the present application. In this specification, schematic representations of the above terms do not necessarily refer to the same embodiments or examples. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.

While embodiments of the present application have been shown and described above, it will be understood that the above embodiments are illustrative and not to be construed as limiting the application, and that variations, modifications, alternatives and variations may be made to the above embodiments by one of ordinary skill in the art within the scope of the application.

Claims

1. A one-stop database job management method, comprising:

2. The method according to claim 1, wherein the method further comprises:

3. The method of claim 1, wherein upon receiving a work order submitted by a user, the method further comprises:

4. The method of claim 1, wherein executing the corresponding approval process according to the work order type comprises:

determining the influence range of the work order type;

5. The method of claim 1, wherein executing the work order comprises:

6. The method of claim 1, wherein executing the work order further comprises:

7. The method of claim 1, wherein monitoring and displaying the work order execution progress comprises:

determining the type of a database corresponding to the work order;

8. The method according to claim 1, wherein the method further comprises:

and recording the execution process and the execution result of the work order.

9. A one-stop database job management platform, comprising:

a processor and a memory;

the processor is connected with the memory through a communication bus:

the memory is used for storing a program at least for executing a one-stop database management method according to any one of claims 1 to 8.