KR101636026B1

KR101636026B1 - System and method for destructing and removing privacy data

Info

Publication number: KR101636026B1
Application number: KR1020150095186A
Authority: KR
Inventors: 이창하
Original assignee: 주식회사 바넷정보기술
Priority date: 2015-07-03
Filing date: 2015-07-03
Publication date: 2016-07-05

Abstract

The present invention relates to a system and method for destroying and separately storing privacy information. An embodiment may provide a system for destroying and separately storing privacy information, wherein the system includes a program for destroying and separately storing privacy information, which is loaded in the memory and is executed under the control of the processor. The program can perform: a target customer determination function of receiving, from a first database (DB), a list of target customers, which is to be destroyed or separately stored, and identifying the target customers; a target data determination function of receiving, from the first DB, target data to be destroyed or separately stored, and determining the target data; a schedule management function of receiving information on a schedule on which the determined target data is destroyed or separately stored, and registering the schedule; and an execution function of executing an operation of destroying or separately storing the determined target data.

Description

SYSTEM AND METHOD FOR DISPOSING AND DISTRIBUTING PERSONAL INFORMATION [0002]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method for processing personal information, and more particularly, to a system and method for discarding and separating personal information.

Recently, the Personal Information Protection Act was enacted to unify the legal system for protecting personal information and to strengthen the protection of personal information. In addition, various laws and ordinances such as the Credit Information Act, the Electronic Commerce Law, the Medical Law, .

According to these laws, public institutions, financial institutions, and corporations in general must destroy personal information of the customer who has completed the purpose of processing personal information and personal information of the customer when they are no longer needed, without delay , And should be stored and managed separately from other personal information when it is required to preserve it in accordance with the law.

Especially, customer information of a customer whose transaction has been terminated in a recent bankruptcy of customer information of a credit card company is stored together with personal information valid in a database management system (DBMS), causing more damage. In order to compensate, The need to destroy and keep personal information is continuously increasing because it can minimize these damages by severing and controlling the idle accounts of the company.

However, many companies purchase and operate products from various DBMS vendors. Therefore, in order to construct a DBMS for separate storage, all DBMS vendors' products should be purchased and a backup DB should be constructed. In this case, There is a problem that takes a lot of time.

1. Korean Published Patent Application No. 2015-0021239 (published on March 2, 2015) 2. Korean Patent Publication No. 2012-0089917 (published on Aug. 16, 2012)

According to an embodiment of the present invention, a DBMS of a low-cost single vendor product can be constructed, and a DBMS and method for collecting and archiving various DBMSs of an existing DBMS in one DBMS can be provided.

According to an embodiment of the present invention, there is provided a personal information destruction and storage system and method capable of systematically providing and supporting functions such as identification, confirmation, payment, destruction / separation and storage of personal information, and verification .

According to an embodiment of the present invention there is provided a personal information destruction and storage system comprising a computer having a processor and a memory, said system comprising a personal information destruction and separation storage program loaded and executed in the memory under the control of the processor A target customer determination function for receiving a list of target customers to be destroyed or separated and stored from the first database (DB) to identify a target customer; A target data determination function for receiving target data to be destroyed or detached and storing the target data and determining the target data; A schedule management function for receiving and registering schedule information for performing the digestion or archiving of the determined target data; And an execution function of executing the deleting or deleting of the determined target data. [0100] The personal information destruction and storage system may be provided.

According to an embodiment of the present invention, there is provided a method for personal information destruction and separation and storage by a personal information destruction and separation / storage program loaded into a memory under the control of a processor of a computer, the method comprising the steps of: (a) Receiving a list from a first database (DB) and identifying a target customer; (b) receiving data to be destroyed or separated and stored from the first DB and confirming target data; And (c) discarding the determined target data for the identified target customer or separately storing the determined target data in the second database (DB). have.

According to one embodiment of the present invention, there is an advantage that a low-cost single vendor product DBMS is constructed and various DBMSs of an existing periodical system operating system are collected in one DBMS for backup and management, thereby reducing system construction cost and effort.

According to an embodiment of the present invention, it is possible to systematically provide and support functions such as identification, confirmation, payment, destruction / separation and storage of personal information, and verification.

1 is a block diagram for explaining a personal information destruction and separation / storage system according to an embodiment of the present invention;
2 is an exemplary block diagram of a personal information destruction and separation storage system according to one embodiment;
FIG. 3 is an exemplary flow chart for establishing a customer for destruction and separation / storage of personal information according to an embodiment;
FIG. 4 is an exemplary flow chart for determining target data for destruction of personal information and separation and storage according to an embodiment;
5 is a diagram for explaining a meta-management function according to an embodiment,
FIG. 6 is an exemplary flow chart for schedule and payment of personal information destruction and separation and storage operations according to an embodiment;
FIG. 7 is an exemplary flow chart for performing the destruction and storage of personal information according to one embodiment.

BRIEF DESCRIPTION OF THE DRAWINGS The above and other objects, features, and advantages of the present invention will become more readily apparent from the following description of preferred embodiments with reference to the accompanying drawings. However, the present invention is not limited to the embodiments described herein but may be embodied in other forms. Rather, the embodiments disclosed herein are provided so that the disclosure can be thorough and complete, and will fully convey the scope of the invention to those skilled in the art.

In this specification, when an element is referred to as being on another element, it may be directly formed on another element, or a third element may be interposed therebetween.

Where the terms first, second, etc. are used herein to describe components, these components should not be limited by such terms. These terms have only been used to distinguish one component from another. The embodiments described and exemplified herein also include their complementary embodiments.

And is not intended to limit the present invention. In the present specification, the singular form includes plural forms unless otherwise specified in the specification. The terms "comprises" and / or "comprising" used in the specification do not exclude the presence or addition of one or more other elements.

Hereinafter, the present invention will be described in detail with reference to the drawings. In describing the specific embodiments below, various specific details have been set forth in order to explain the invention in greater detail and to assist in understanding it. However, it will be appreciated by those skilled in the art that the present invention may be understood by those skilled in the art without departing from such specific details. In some instances, it should be noted that portions of the invention that are well known in the description of the invention and not significantly related to the invention do not describe confusion in describing the present invention.

1 is a block diagram for explaining a personal information destruction and separation / storage system according to an embodiment of the present invention.

Referring to FIG. 1, a personal information destruction and storage system 100 according to an exemplary embodiment of the present invention is configured to be able to communicate with an operating system 200 and a separate storage server 300. The operating system 200 may include any field of legacy systems to which the present invention applies and a database (DB) 210 managed thereby. For example, the operating system 200 may be one of a national public system, a financial system, a medical system, and a personnel service system managed by a country, a municipality, a financial institution, and various companies. Personal information such as education and training information, communication information, location information, family information, real estate information, income information, credit information, medical information, physical information, and employment information of an individual can be stored.

The operating system 200 stores and manages such information in the DB 210 for a predetermined period of time. For example, at the end of a transaction or when a business purpose is accomplished, the information is directly discarded according to a statute, or the database 210 ). For example, in the case of the financial sector, according to the Credit Information Act, the collection and processing of credit information should be kept for a maximum of three years and destroyed within a maximum of five years from the date on which the reason for resolution has been resolved. According to the records, the medical record should be kept for 10 years, and the video record or opinion kept for 5 years and destroyed.

The personal information destruction and storage system 100 according to an embodiment of the present invention may directly discard information stored in the DB 210 according to various laws and regulations of the field when the system 100 is applied to a specific field, Or moved to the DB 310 of the separation and storage server 300, separated and stored for a predetermined period, and then destroyed.

FIG. 2 is an exemplary block diagram of a personal information destruction and storage system 100 according to one embodiment, and is a block diagram illustrating the functional hierarchy of a personal information destruction and storage system 100 according to one embodiment.

Referring to the drawings, a system 100 includes an operating system (OS) 10, a web application server (WAS) layer 20, and an application 30. The system 100 includes various hardware such as a processor, a memory and the like, and may further include any platform or framework for driving an application, but the description and illustration of components not directly related to the present invention are omitted herein Those skilled in the art will appreciate that, in addition to the components shown in the figures, system 100 may further comprise other hardware and / or software as needed.

The OS 10 may be any operating system, and may use Linux in one embodiment. The WAS layer 20 provides an execution environment of the application 30 and provides a connection function to the database 50 and a communication function with the operation system 200 or the separate archive server 300. In one embodiment, the WAS layer 20 may comprise a platform including WAS / HTTP, Java database connectivity (JDBC), SQL * NET, and Tabular Data Stream (TDS).

The WAS / HTTP is a functional unit for the system 100 to function as a web application server and / or a web server. For example, the user can access the DB 50 through a service provided by the WAS. The JDBC is an application program interface (API) that enables SQL to be executed in a Java (JAVA) program to access the DB 50. SQL * Net is Oracle's remote data access software that enables client-server and server-server communication over any network. TDS is a communication protocol used by database servers and application applications to communicate with each other .

The WAS layer 20 according to an embodiment provides a platform function for a user to communicate with the operating system 200 or the separate archive server 300 and access the DB 50 in the system 100 itself, At least some of the illustrated components (WAS / HTTP, JDBC, SQL * NET, etc.) may be omitted or other protocols or interfaces may be added in addition to these components in accordance with a specific embodiment.

The application 30 includes a program for personal information destruction and separate storage according to an embodiment of the present invention. The application 30 provides a user interface 35 for receiving a command from a user and displaying a result of executing a program, and can perform various functions for personal information destruction and separation and storage by a user command or the like. In one illustrative embodiment, this functionality includes, for example, functions such as job management 31, meta management 32, schedule and payment management 33, and execution and monitoring 34.

In one embodiment, the task management 31 may include an object customer identification function and an object data identification function. The target customer identification function identifies the customer for the destruction or separate storage of personal information and confirms the object to be processed. The target customer identification function according to the embodiment allows the DB 210 of the operating system 200 to provide a list of target customers to be discarded or separately stored and can identify and confirm the target customer. In general, since personal information is used for a plurality of tasks, the target customer identification function has to set a plurality of selection criteria based on a plurality of tasks and confirms the target client by using an SQL command for identifying the target customer for each selection criterion .

The target data identification function identifies the data to be destroyed or detached and confirms the object to be processed. According to this function, target data to be destroyed or separated and stored can be received from the DB 210 and the target data can be determined. As an example, target data for identifying target data to be destroyed or detached and archived, Can be confirmed.

For example, when the DB 210 is implemented by a plurality of types of DBMS products, the meta management 32 analyzes the table structure of each DBMS, You can create and manage.

As an example of meta-management, a database catalog of each DBMS can be collected and a metadata DB can be generated based on the collected database catalog. Also, it is possible to compare the collected database catalog with the previously stored data in the metadata DB to judge whether a table of each DBMS is added or changed, and update the metadata DB based on the determination.

The schedule and approval management (33) includes a schedule management function for receiving and registering schedule information for performing the destruction or separation and holding of the target data, and a payment function for confirmation, approval and approval of the manager before execution of the destruction and separation / Lt; / RTI >

Execution and monitoring 34 may have the function of executing the destruction or detachment of confirmed target data and monitoring and displaying the execution process and execution result.

The application 30 may further include functions other than those described above. For example, the application 30 may further include a verification function for verifying whether the personal information destruction and separation keeping job has been correctly processed, and a report function for creating and outputting a report according to the execution of the destruction and separation and storage job.

The database (DB) 50 is a storage unit that stores at least a part of data used when the system 100 performs the above-described functions. In the illustrated embodiment, the DB 50 includes a job management DB 51, a payment management DB 52, a meta management DB 53, a log management DB 54, and a schedule management DB 55.

The work management DB 51 can store the data required for identification and confirmation of the target customer and the identification and determination of the target data (for example, a list of target customers fetched from the DB 210 of the operating system, a list of target data, etc.) . The approval management DB 52 can store data for approval and approval by the user and the administrator in the personal information destruction and separation and storage work. The meta management DB 53 may store a database catalog collected from each DBMS managing the DB 210 of the operating system 200 and a metadata database generated based on the database catalog. The log management DB 54 can store a record of connection to the system 100 of a user or an administrator and the like and the schedule management DB 55 can store schedules related to personal information destruction and separation and storage work. The above-described DBs 51 to 55 may be integrated with each other according to a specific embodiment, some of them may be omitted, or other databases may be added.

Although the hardware of the system 100 is not shown in detail in the drawing, those skilled in the art will appreciate that various functions of the above-described application 30 are actually written in, for example, program code, loaded into a memory (not shown) As will be appreciated by those skilled in the art. That is, these program codes are stored in an arbitrary storage device (not shown) in the system 100 and are loaded into a memory under the control of a processor (not shown) of the system 100, Can be executed.

Hereinafter, the main functions of the application 30 will be described with reference to FIGS. 3 to 7. FIG.

Target customer identification features

The target customer identification function is a function for identifying a target customer to be destroyed or separated and to be determined and a target to be processed by the target customer identification function of the job management 31. The target customer identification function extracts a list of target customers to be destroyed or separated and stored from the DB 210 Identify and confirm the customer. In this regard, FIG. 3 illustrates an exemplary flow chart for establishing a customer for destruction and separation and storage of personal information according to one embodiment.

3, in step S110, an identification SQL for the target customer identification is created and transmitted to the DBMS managing the DB 210 of the operating system. Then, in step S120, the target customer list is transmitted from the DBMS And calculates the analysis result.

In general, since the criteria for destroying personal information or separating and storing are applied differently according to the types of business according to the standards set by various laws and regulations, in order to identify the customer data to be destroyed and separated according to these various standards, Identifies the target customer based on an identification SQL command for each selection criterion of a plurality of selection criteria according to a plurality of tasks.

For example, assuming that the system 100 of the present invention is applied to a bank, a bank may have services such as reception, credit, foreign exchange, and so on. For example, as shown in Table 1 below, customer 1 should be judged to be a transaction customer as a result of comprehensive judgment because the transaction is terminated in the credit business and foreign exchange business but still in the receiving business. In other words, the analytical SQL for identifying each task is defined and the results are compared again, and it is necessary to judge the customer as a termination customer when it is judged as a termination customer.

goddess reception Foreign exchange Judgment result Customer 1 destruction maintain destruction maintain Customer 2 destruction destruction destruction destruction Customer 3 maintain maintain maintain maintain

Accordingly, in step S110, an SQL command is generated for each of a plurality of selection criteria according to a plurality of tasks, and the SQL command is transmitted to the DBMS. After receiving the client list according to the result, As a result, the analysis results are comprehensively analyzed.

Thereafter, in step S130, the customer's confirmation of the customer list analyzed in step S120 is received. For example, displaying the analyzed customer list allows the administrators to review the list and enter a selection command to the system 100 via the user interface 35 to select the customer as a destruction / detachment target customer, It is possible to confirm the customer to be destroyed / separated (step S140).

On the other hand, data such as a SQL command for each task for identifying a destruction and separation holding customer and data such as a customer list extracted from the DB 210 can be registered in, for example, the job management DB 51 and used repeatedly.

Target data identification function

The target data identification function is a function for identifying the destruction / separation storage target data of the job management 31 and confirming the processing target. For example, the target data to be destroyed or separated and stored is received from the DB 210 to confirm the target data. In this regard, FIG. 4 shows an exemplary flowchart for determining data to be subjected to destruction and separation / storage of personal information according to an embodiment.

Referring to the drawing, in step S210, a schema of a target table for destruction / separation storage is registered. Here, the target table may be, for example, a ledger table including various customer information of the DB 210 of the operating system, and a policy for discarding and separating and storing the corresponding table and / (For example, in the job management DB 51 or the meta management DB 53).

Next, in step S220, an identification SQL that identifies data to be deleted and stored is transmitted to the DBMS managing the DB 210 of the operating system, and the object data is received from the DBMS in step S230. The system 100 displays the received object data on the screen and receives confirmation from the manager. The administrator can input the confirmation command for reviewing the target data and selecting and confirming it as target data of destruction / separation storage in the system 100 via the user interface 35, and accordingly, in step S240, 100) receives the confirmation command, it is possible to finally determine the destruction / separation storage target data (step S250).

On the other hand, data such as an SQL command for identifying the data to be destroyed and separated and stored may also be registered in the job management DB 51 for later use.

Meta management function

The meta management manages meta data of a database. For example, when the DB 210 is implemented by a plurality of types of DBMS products, the DB of the respective DBMSs can be analyzed to generate and manage the DB of the meta data.

The general meta-management system should register and manage the table designers for standardization and configuration management. However, if this is done, the business process should be changed and the standardization work should be done. Accordingly, the personal information destruction and storage system 100 according to an embodiment of the present invention has a schema import function for automatically analyzing the table structure in the DBMS and building a database of metadata.

5, a database catalog is collected from DBMSs of various DBs 210 operated in the operating system 200, and a metadata database 63 is generated based on the collected database catalogs can do. The generated metadata DB 63 can be stored in the meta management DB 53, for example.

By managing the metadata according to each DBMS, for example, when the personal information destruction and separation and storage system 100 performs the target data check operation of FIG. 4, even if the operating system 200 is composed of various kinds of DBMSs, (100) can communicate with each DBMS of the operating system (200) to extract and process DB data.

The DB 210 of the operating system 200 may be constantly added and changed. The meta management 32 according to an embodiment compares the table structure with the addition and / or modification of the DB, It can be automatically identified. That is, it is possible to compare the database catalog collected from the operating system 200 with the previously stored data in the metadata DB 63 to determine whether the table of each DBMS is added or changed, and update the metadata DB based on the determination.

In one embodiment of the present invention, the table change history thus identified is stored and reviewed by the administrator, thereby identifying and managing the personal information only for the changed items without having to conduct the entire survey every time, thereby minimizing the time and cost for managing the metadata have.

Ability to identify tables and columns where personal information is stored

Meanwhile, when generating and managing the metadata of the database 210 by analyzing the table structure of the DB 210 of the periodical system operating system 200 through the above-described meta-management function, the personal information of the DB 210 is stored It is important to detect.

In this case, information of some tables or columns is not treated as personal information due to user's mistakes or omissions. In this case, There is also a problem that the management cost is increased. In an embodiment of the present invention, at least one of the following two methods can be used to solve this problem.

In the first method, a rule for identifying a column storing personal information is defined by using a naming rule, a data type, a length, and the like for each column, and by applying this rule, The stored column can be detected.

For example, in the case of the naming rule of the column, the customer number is often referred to as "CUST_NO" and the customer name is referred to as "CUST_NM" as shown in the database 63 of FIG. 5, A list of various symbols used as a column name for storing personal information and a rule for the kind of personal information stored in each symbol can be defined and provided in advance.

It is also possible to determine whether the personal information is stored using the length or type of the data stored in the column. For example, a column in which a 13-digit number string is stored (or a column in which a 6-digit string, a hyphen, and a 7-digit string are arranged in order) can be determined as a column in which a customer's social security number is stored. As another example, information stored in a specific column may be set to be recognized as personal information such as a resident registration number, a date of birth, a name, and the like depending on data types such as numbers, letters, and date formats.

Next, the second method for identifying the table and the column in which the personal information is stored is to define the pattern of the data according to the type of the personal information in advance, and to identify the data related to the personal information in the metadata DB using this pattern.

In one embodiment, a pattern of each personal information can be defined using a regular expression for personal information such as a customer's name, resident registration number, telephone number, and e-mail address. For example, in the case of a resident registration number, the first six digits before the hyphen ("-") are the date format and the seventh digit has a value of 1 to 4 depending on the gender. Accordingly, the pattern of the resident registration number is a regular expression Can be expressed.

As another example, for an email address, there is a rule that "@" is used after the mix of alphanumeric and special characters followed by a string of zero followed by at least one period (".") In the string , So you can express the pattern for the email address as a regular expression.

If at least one of the above methods is applied when managing the metadata as described above, the personal information can be automatically searched and informed to the administrator, thereby preventing the problem that the personal information is stored in the column due to the mistake of the manager or the management omission can do.

Schedule and approval management function

The schedule and approval management (33) may have a schedule management function for receiving and registering schedule information for performing the destruction or separation / holding work of the target data, and a settlement function for receiving approval from the administrator before execution of the destruction and separation / storage job.

FIG. 6 shows an exemplary flow chart for schedule and approval of personal information destruction and separation and storage operations according to an embodiment. First, in step S310, the user registers a work project for personal information destruction and separate archive. At this stage, for example, a new job for personal information destruction and separate storage is registered in the system 100.

Thereafter, in step S320, the execution schedule of the corresponding project is set by registering the scavenging and separation holding job schedule of the registered project. The task execution may be executed immediately after completion of the target customer confirmation and target data expansion described with reference to FIGS. 3 and 4, or may be set to be executed after a certain period of time.

Next, in step S330, the settlement of the destruction and separation keeping project is exited, and in step S340, the administrator approves the settlement. Steps S330 and S340 may be performed by, for example, displaying the approval upper screen on the display of the user interface 35 and inputting a settlement instruction through the user interface 35 by the administrator.

Execution and monitoring functions

FIG. 7 is an exemplary flow chart for performing the destruction and storage of personal information according to one embodiment. Referring to FIG. 4, in step S410, it is determined whether or not the execution time of the personal information destruction and separation / storage job according to the predetermined schedule is the execution time. If it is determined to be the job execution time, the flow advances to step S420 to transmit the extracted SQL for extracting the destroyed and separated archive data to the DBMS of the operating system 200 in step S420. The extracted SQL at this time may be, for example, the target customer identification SQL registered at the time of finalizing the target customer described in FIG. 3 and the target data identification SQL registered at the time of finalizing the target data described in FIG.

Thereafter, in step S430, the data extracted from the DB 210 is received in response to the extraction SQL, and the data extracted in step S440 is subjected to the destruction and / or separation / storage operation. That is, the confirmed target data for the determined target customer is discarded or transmitted to the DB 310 for separation and storage. Such a destruction and separation / storage job is displayed in real time on the display screen of the user interface 35 and the execution result is displayed after execution of the job (step S450).

As described above, although the present invention has been described with reference to the limited embodiments and drawings, the present invention is not limited to the above embodiments. It will be understood by those skilled in the art that various changes and modifications may be made by those skilled in the art without departing from the spirit and scope of the invention. Therefore, the scope of the present invention should not be limited by the described embodiments, but should be determined by the equivalents of the appended claims, as well as the appended claims.

10: Operating system
20: WAS layer
30: Application
35: User interface
50: Database
100: Personal information destruction and separation system
200: Operating System
300: Separate archive server

Claims

A personal information destruction and storage system comprising a computer having a processor and a memory, the system comprising a personal information destruction and detachment storage program loaded and executed in the memory under the control of the processor,
A target customer determining function of receiving a list of customers to be destroyed or separated and stored from a first database (DB) to identify a target customer;
A target data determination function for receiving target data to be destroyed or detached and storing the target data and determining the target data;
A schedule management function for receiving and registering schedule information for performing the digestion or archiving of the determined target data; And
And an execution function for executing the destruction or separation keeping operation of the determined target data,
Wherein the target customer determining function is to determine the target customer based on an identification SQL command for each selection criterion of a plurality of selection criteria for a plurality of jobs.

delete

The data processing apparatus according to claim 1,
Wherein the target data is determined based on a target data identification SQL command for identifying data to be destroyed or separated and stored.

The method according to claim 1,
And a meta management function for analyzing a table structure of each DBMS and generating a DB of the metadata when the first DB is implemented as a plurality of DBMS products, .

5. The method of claim 4,
And collects the database catalogs of the respective DBMSs and generates the metadata DB based on the collected database catalogs.

6. The method of claim 5,
Comparing the collected database catalog with the previously stored data in the metadata DB to determine whether the table of each DBMS is added or changed, and updating the metadata DB based on the determined result. Separate storage system.

6. The method of claim 5,
A rule for identifying a column in which personal information is stored by using at least one of a naming rule, a data type, and a data length for a column of the database is defined, and data related to the personal information is detected Wherein the personal information destruction and separation and storage system comprises:

6. The method of claim 5,
Wherein a pattern of data according to the type of personal information is defined in advance and data associated with personal information can be detected from the metadata DB using the pattern.

A personal information destruction and storage method using a personal information destruction and separation / storage program loaded and executed in a memory under the control of a processor of a computer,
(a) receiving a list of customers to be destroyed or separated from a first database (DB), and identifying a target customer;
(b) receiving data to be destroyed or separated and stored from the first DB and confirming target data; And
(c) discarding the determined target data for the identified target customer or separately storing the determined target data in a second database (DB)
Wherein the step (b) is to determine the target data based on a target data identification SQL command for identifying target data to be destroyed or detached or archived.

10. The method of claim 9,
(d) judging whether or not the execution of the personal information destruction and separation storage execution time according to the predetermined schedule,
Wherein the step (a) to (c) is executed when it is determined that the execution time is the execution time.

10. The method of claim 9,
Wherein the step (a) identifies the target customer based on an identification SQL command for each selection criterion of a plurality of selection criteria according to a plurality of tasks.

delete

10. The method of claim 9,
(e) analyzing a table structure of each DBMS to generate a DB of the metadata when the first DB is implemented as a plurality of DBMS products before the step (a) , Personal information destruction and separate storage methods.

14. The method of claim 13,
Wherein the step (e) collects database catalogs of the respective DBMSs and generates the metadata DB based on the collected database catalogs.

15. The method of claim 14, wherein step (e)
Comparing the collected database catalog with previously stored data in the metadata DB to determine whether a table of each DBMS is added or changed; And
And updating the metadata DB based on a result of the determination.