KR102046567B1 - Real-time DDL generation method for standard dictionary-based metadata change management - Google Patents

Abstract

Based on the standard dictionary, table data modeled by various modeling tools is compared with the history accumulated in the solution in real time to create data about new, modified, and deleted, and based on this, to generate DDL for the repository in real time. A method for generating real-time DDL for standard dictionary-based metadata change management. Registering basic dictionary information to create a standard dictionary to build a standard dictionary, and modeling with a modeling tool based on the standard dictionary information. Entering information about the modeling tool in progress, checking the standard based on the registered standard dictionary of the modeled table data, selecting the applied table, and requesting approval from the database administrator (DBA) when the approval is completed. Once this is done, the history of the solution is By including the step of automatically generating a data definition language (DDL), implements a real-time DDL generation method for a standard dictionary-based metadata change management.

Description

Real-time DDL generation method for standard dictionary-based metadata change management

The present invention relates to a method for generating real-time DDL (Data Definition Language) for standard dictionary-based metadata change management. In particular, the data modeled by various modeling tools based on the standard dictionary is compared with the history accumulated in the solution in real time. The present invention relates to a real-time DDL generation method for standard dictionary-based metadata change management that creates data for new, modified, deleted, and generates DDL in real time based on the repository.

Structured data about data, using metadata as data that describes other data. Metadata is also called attribute information. It is data that is given to content according to a predetermined rule in order to efficiently find and use information that is being searched among a large amount of information.

For metadata change management, a database administrator (DBA) visually determines data definition language (DDL) and consistency for applying metadata change technology to a database.

A conventionally proposed technique for managing metadata for metadata change management is disclosed in the following Non-Patent Document 1.

The prior art disclosed in <Non-Patent Document 1> proposes effective management techniques for a metadata server cluster that effectively distributes and manages metadata information for a large-capacity distributed file system. To effectively protect and use the locality of file system namespaces to provide better metadata retrieval, we propose a dictionary partitioning scheme (DicPS) for managing metadata partitioning. This paper proposes a load balancing technique based on the metadata partitioning scheme proposed to adapt to dynamically changing workloads, and replicates metadata and partitions metadata to dynamically adapt to the evolution of the file system and the load on the metadata server. Changes in summary information are used to improve performance in scalability and load balancing.

(Non-Patent Document 1) Chungbuk National University, Information and Communication Engineering, Graduate School of Information and Communication Engineering 2009. 2, Ph.D. Dissertation "Effective Metadata Management for Massive Distributed File System)

However, the above-described DDL generation technology by the general DBA generates DDL by manually checking the DBA for metadata change management by checking whether the table is actually present or not, and if any changes have been made. There are a lot of mistakes and errors, and there is a disadvantage that the DDL generation time is complicated and complicated.

In addition, the prior art disclosed in <Non-Patent Document 1> is capable of effectively distributing and managing metadata information for a large-capacity distributed file system, but has a disadvantage in that a technology for generating DDL for metadata change management cannot be provided. .

Therefore, the present invention has been proposed to solve all the problems occurring in the prior art as described above. Its purpose is to provide a real-time DDL generation method for standard dictionary-based metadata change management that creates data in real time and generates DDL in real time based on it.

In order to achieve the above object, the real-time DDL generation method for standard dictionary-based metadata change management according to the present invention comprises the steps of: (a) registering the basic dictionary information for creating a standard dictionary to build a standard dictionary; (b) inputting information on the modeling tool, and modeling the modeling tool based on the constructed standard dictionary information; (c) checking whether the table data modeled in step (b) is standard based on the standard dictionary registered in step (a); (d) After selecting the table applied, selecting the desired payment line, and applying for payment, when the payment of the payers included in the payment line is completed, it is finally requested by the database administrator (DBA) for approval. And automatically generating a data definition word (DDL) for the requested table based on the history of the solution.

Wherein (a) step (a1) generating a word for the standard dictionary; (a2) generating a domain based on the generated word; (a3) generating a term by designating a table or a column based on the generated word and the generated domain information.

The modeling tool of step (b) is characterized by using any one of DA # 5, Erwin 7, Power Designer 9, ER-Win9 Genesis, ER-Win9 Softverk.

In the step (c), it is determined whether the standard is based on the registered standard dictionary in which the modeled table data is registered, and whether the table can be applied for and the changes are examined.

The change in the above is characterized by checking whether the table is new, deleted, or modified.

In step (d), (d1) applying for a table; (d2) identifying a target database for metadata change management; (d3) executing database script logic; (d4) if the change of the requested table is a new table, determining a new table; (d5) if the requested table is not a new table, checking whether the change is deleted and dropping the table (DROP) if it is deleted; (d6) if the change of the requested table is not a new table or a delete, checking whether the change is an ALTER request and changing the table if the change is requested; (d7) if the requested table is not a change request, dropping the table and creating a new table.

The database administrator of step (d) is approved in the DDL generation screen, characterized in that to apply the DDL by applying buttons according to the development system, test system, operating system and check the log (Log).

According to the present invention, since DDL is automatically generated in real time according to the metadata change management, the DBA can eliminate the trouble of manually checking whether the table exists or not, and if any changes have been made by hand. In addition, there is an advantage that can prevent mistakes or errors due to manual work, and also shorten the DDL generation time.

Further, according to the present invention, since the DBA can immediately check the generated DDL and apply it to the database, there is an advantage of reducing the risk of a mistake error and the probability of inconsistency.

1 is a flowchart showing a real-time DDL generation method for standard dictionary-based metadata change management according to the present invention;
FIG. 2 is a flowchart illustrating a specific embodiment of a method for generating a real-time DDL for managing change of standard dictionary-based metadata of FIG. 1;
3 is a flowchart illustrating an embodiment of a DDL generation process of FIG. 2;
4 is a screen example for registering a modeling tool to be used in the present invention;
5 is an application example of a modeling tool in the present invention,
6 is an exemplary diagram of table data modeled using a modeling tool in the present invention;
7 is a table application example in the present invention,
8 is an exemplary view illustrating a selection line in the present invention;
9A and 9B are exemplary diagrams of a DDL screen generated in the present invention.

Hereinafter, a method for generating real-time DDL for standard dictionary-based metadata change management according to an exemplary embodiment of the present invention will be described in detail with reference to the accompanying drawings.

1 is a flowchart illustrating a real-time DDL generation method for standard dictionary-based metadata change management according to an exemplary embodiment of the present invention, where S represents a step.

The real-time DDL generation method for standard dictionary-based metadata change management according to the present invention comprises the steps of: (a) registering basic dictionary information to create a standard dictionary to build a standard dictionary (S10), (b) a modeling tool in use Inputting information about the model, and modeling with the modeling tool based on the constructed standard dictionary information (S20), (c) registering the table data modeled in step (b) in step (a) Step (S30) of checking the standard based on the standard dictionary, (d) selecting the applied table and requesting approval from the database administrator (DBA) when the approval is completed, and if the approval is made, the solution of the applied table is Automatically generating data definition words (DDL) based on the history (S40, S40).

The real-time DDL generation method for standard dictionary-based metadata change management according to the present invention configured as described above will be described in detail.

First, in step S10, a user for applying a metadata change technique to a database registers basic dictionary information for creating a standard dictionary to build a standard dictionary. To construct a standard dictionary, as shown in FIG. 2, a word for the standard dictionary is generated (S11), and a domain is generated based on the generated word (S12). Subsequently, a term is generated by designating a table and a column based on the generated word and the generated domain information. The term you create becomes the term defined in the standard dictionary.

After the standard dictionary is registered, the user models in step S20 using any one of known modeling tools DA # 5, Erwin7, Power Designer 9, ER-Win9 Genesis, and ER-Win9 Softverk (S21 in FIG. 2). For the table data modeled here, it is preferable to input information about the modeling tool in use and to import the table data for each modeling tool. 4 is a diagram illustrating a screen for registering a modeling tool to be used, FIG. 5 is a diagram illustrating an application of a modeling tool, and FIG. 6 is a diagram illustrating table data modeled using a modeling tool.

Next, it is determined whether the table data modeled using the modeling tool in step S30 based on the standard dictionary registered in step S10. It also checks the availability of the table and the changes. Here, the change checks whether the table is new, deleted, or modified. 5 illustrates an example of modeling table data using a modeling tool.

Next, if it is determined that the application of the table is possible as a result of the checking in step S30, go to step S40, select the applied table, select the settlement line, and when the settlement is completed, grant the approval to the final database administrator (DBA). Request (S41, S51).

7 is an exemplary view of applying for a table in the present invention, Figure 8 is an illustration of the selection line selection.

Subsequently, when approval is made by the final database manager, a data definition word (DDL) is automatically generated based on the history of the solution for the applied table (S52).

FIG. 3 is a detailed flowchart illustrating the DDL generation process of FIG. 2.

When the table is requested in step S71, the target database for metadata change management is checked in step S72. Then, the database script logic is executed in step S73. Next, if the requested table is a new table in step S74, the process moves to step S75 to determine a new table. In contrast, if the requested table is not a new table, the process moves to step S76 to check whether the change is deleted, and if the change is deleted, the process moves to step S77 to drop the table. If the requested table is not a new table or is not deleted, the process moves to step S78 to check whether the request is a change (ALTER). In addition, if the requested table is not a change request, the process proceeds to step S80 to drop the application table, and to step S81 to create a new table.

In this process, the requested table is automatically generated based on the solution history. 9A and 9B are diagrams illustrating actually generated DDL screens and examples of DDL for managing metadata change in a bank database.

After automatically generating the DDL, in step S63, the final database manager applies the approved and generated DDL to the database. That is, the final database manager approves in the DDL creation screen, applies the DDL with the apply button according to the development system, test system, and operation system, and checks the log.

Since the present invention automatically generates the DDL according to the metadata change management in real time, the DBA can eliminate the hassle of manually checking whether the table is actually present or not, and if any changes have been made by hand. In addition, it can prevent mistakes or errors caused by manual operations and shorten the time for generating DDL.

In addition, since the DBA can immediately check the generated DDL and apply it to the database, it is possible to reduce the risk of mistake error and the probability of inconsistency.

Although the invention made by the present inventors has been described in detail according to the above embodiments, the present invention is not limited to the above embodiments, and various modifications can be made without departing from the spirit and scope of the present invention. Self-evident to those who have

Claims (7)

As a method of generating data definition words (DDL) in real time for metadata change management based on a standard dictionary,
(a) registering a basic dictionary information for creating a standard dictionary to build a standard dictionary;
(b) modeling with a modeling tool based on the constructed standard dictionary information, and inputting information on the modeling tool in use;
(c) checking whether the table data modeled in step (b) is standard based on the standard dictionary registered in step (a); And
(d) Selecting the requested table and requesting approval from the database administrator (DBA) when the payment is completed, and automatically generating data definition words (DDL) for the requested table based on the solution history. Including steps
In the step (c), it is determined whether the standard is based on the registered standard dictionary of modeled table data, and the real-time DDL for the standard dictionary-based metadata change management, characterized in that the application of the table and the change is examined. How to create.
The method of claim 1, wherein step (a) comprises: (a1) generating a word for a standard dictionary; (a2) generating a domain based on the generated word; (a3) real-time DDL generation method for standard dictionary-based metadata change management, comprising generating a term by specifying a table and a column based on the generated word and the generated domain information.
The method of claim 1, wherein the modeling tool of step (b) uses any one of DA # 5, Erwin7, Power Designer 9, ER-Win9 Genesis, ER-Win9 Softverk. Real time DDL generation method.
delete 2. The method of claim 1, wherein the change checks whether a table is new, deleted, or modified. 3.
The method of claim 1, wherein step (d) comprises: (d1) requesting a table; (d2) identifying a target database for metadata change management; (d3) executing database script logic; (d4) if the change of the requested table is a new table, determining a new table; (d5) if the requested table is not a new table, checking whether the change is deleted and dropping the table (DROP) if it is deleted; (d6) if the change of the requested table is not a new table or a delete, checking whether the change is an ALTER request and changing the table if the change is requested; (d7) if the requested table is not a change request, dropping the table, and generating a new table.
The method according to claim 1, wherein the database manager of the step (d) is approved in the DDL generation screen, based on the standard dictionary, characterized in that applying the DDL with the apply button according to the development system, test system, operating system and check the log (Log) Real-time DDL generation method for metadata change management.

Images