WO2014088396A2 - Automatic transformation of non-relational database into relational database - Google Patents
Automatic transformation of non-relational database into relational database Download PDFInfo
- Publication number
- WO2014088396A2 WO2014088396A2 PCT/MY2013/000216 MY2013000216W WO2014088396A2 WO 2014088396 A2 WO2014088396 A2 WO 2014088396A2 MY 2013000216 W MY2013000216 W MY 2013000216W WO 2014088396 A2 WO2014088396 A2 WO 2014088396A2
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- database
- relationship
- data
- relational database
- tree
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
- G06F16/254—Extract, transform and load [ETL] procedures, e.g. ETL data flows in data warehouses
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
- G06F16/258—Data format conversion from or to a database
Definitions
- the present invention relates to a system and method for automatic transformation of nonrelational database into relational database that is self-reliant.
- Legacy system contains unstructured data as there are different tables, files, or database which is using different format or structure. Data transformation in legacy system remains a hassle task as there is no existence of relationship between the data. In addition, the format of data is defined differently by users. Therefore, more time is required to synchronize data definition and error may occur during data transformation due to invalid definition. The database of legacy system may store corrupted data due to the wrongly defined data format.
- the presently available data transformation system is time consuming in defining the data process, in data structure analysis and data transformation as it requires human intervention. Accuracy of the presently available system is low and thus requires more resources in amending the data. Hence, current solutions are yet to improve the level of trust for analysis and decision making.
- the present invention proposes a system and method that automatically creates relationship between data structures in a system whereby no relationship exist during transformation; to synchronize the structures, type and format between unknown data structures for relationship binding between the data structures and automatically create table and data relationship and perform data transformation without the need for human intervention thus having self-reliant transformation process with higher accuracy of data relationship.
- the approach as proposed in the present invention performs automatic transformation of non-relational DBMS (Database Management System) to RDBMS (Relational DBMS) whereby no relations or key is defined or declared. It consists of a method to perform database analysis on DBMS; mainly but not limited to non-relational DBMS and flat-file; using LA (Lexical Analysis) and Al (Abstract Interpretation).
- the proposed solution will then incorporate a method to identify and construct the relationship between non-relational data using DFA (Data Flow Analysis) techniques together with the result from the previous method.
- DFA Data Flow Analysis
- the solution will automatically create a database, correct and harmonize tables and its structure, and perform data insertion with accurate key identification with a valid data and format.
- the subject matter claimed herein is not limited to embodiments that solve any disadvantages or that operate only in environments such as those described above. Rather, this background is only provided to illustrate one exemplary technology area where some embodiments described herein may be practice.
- the present invention provides a system and method for automatic transformation of nonrelational database into relational database that is self-reliant.
- One aspect of the present invention provides a system for automatic transformation of non-relational database into relational database that is self-reliant.
- the system comprising at least one data analyzer (102); at least one relationship builder (104); and at least one data transformer (106) for automatically transforming non- relational database into relational database.
- the at least one data analyzer (102) having means for analyzing non-relational database and data structure to form database tree while the at least one relationship builder (104) having means for identifying relationship and key and further associating it with database tree to form draft database structure; and evaluating relationship binding to produce confine database structure.
- One aspect of the present invention provides for the at least one data transformer (106) for automatically transforming non-relational database into relational database.
- the at least one data transformer (106) having means for creating database by constructing database, tables and relationship into relational database; and performing data insertion with key identification and valid data format for database transformation.
- the said non-relational database is in DBMS (Database Management System) format and relational database is in RDBMS (Relational Database Management System) format.
- the present invention provides a method (200) for automatic transformation of non-relational database into relational database that is self-reliant.
- the method comprising steps of initializing configuration of transformation process (202); analyzing non-relational database and data structure to form database tree (204); identifying relationship and key and further associating it with database tree to form draft database structure (206); evaluating relationship binding to produce confine database structure (208); creating database by constructing database, tables and relationship into relational database (210); and performing data insertion with key identification and valid data format for database transformation (212).
- Another aspect of the present invention describes the further steps of the method for analyzing non-relational database and data structure to form database tree.
- the said method further comprising steps of reading non-relational database to search for DBMS file (302); extracting table structure from at least one identified DBMS file (304); analyzing source code using Al (Abstract Interpretation) to locate complete table structures which may include field size, type and format (306); and generating AST (Abstract Syntax Tree) using extracted table structure obtained from at least one identified DBMS file and table structure obtained from analysis of source code (308).
- Al Abstract Interpretation
- AST Abstract Syntax Tree
- the present invention provides the further steps of the method for identifying relationship and key and further associating it with database tree to form draft database structure.
- the said method further comprising steps of constructing and loading AST into database tree (402); analyzing at least one identified DBMS file identified in (step 302) with LA (Lexical Analysis) to obtain table references and key (404); generating at least one reference and at least one key based on results obtained through LA in (step 404) wherein a plurality of keys with identical names with different format, type and length is generated; and tagging at least one reference and at least one key obtained to generated database tree to form draft database structure.
- a further aspect of the present invention provides further steps of the method for evaluating relationship binding to produce confine database structure.
- the said method further comprising steps of reading and loading at least one DBMS file into memory (502); performing flow analysis on results obtained through LA in (step 404, 406) using DFA (Data Flow Analysis) to obtain data flow, relationship and field format (504); binding relationship with AST generated in (step 308) and database tree generated from DFA in (step 504) (506); and synchronizing and aligning table structure to produce a confine database structure (508).
- DFA Data Flow Analysis
- the present invention provides further steps for creating database by constructing database, tables and relationship into relational database.
- the said method further comprising steps of generating database scripts from generated AST (602); generating keys based on AST (604); generating relationship script based on DFA and AST (606); and executing database creation based on complete and structured table (608).
- FIG. 1.0 illustrates the block diagram of the architecture of present invention in comparison with the architecture of the legacy system.
- FIG. 2.0 is a flowchart illustrating the method for automatic-transformation of non-relational database into relational database that is self-reliant.
- FIG. 3.0 is a flowchart illustrating the method for analyzing non-relational database and data structure to form database tree.
- FIG. 4.0 is a flowchart illustrating the method for identifying relationship and key and further associating it with database tree to form draft database structure.
- FIG. 5.0 is a flowchart illustrating the method for evaluating relationship binding to produce confine database structure.
- FIG. 6.0 is a flowchart illustrating the method for creating database by constructing database, tables and relationship into relational database.
- FIG. 1.0 illustrates the block diagram of the architecture of present invention in comparison with the architecture of the legacy system
- FIG. 2.0 is a flowchart illustrating the method for automatic- transformation of non-relational database into relational database that is self-reliant. As illustrated in FIG.
- the system of the present invention comprising at least one data analyzer (102); at least one relationship builder (104); and at least one data transformer (106) for automatically transforming non-relational database into relational database.
- the present invention is applicable in any database transformation and in any environment provided that the source and target are available and accessible by the solution.
- the system as proposed in the present invention can be invoked from any defined host and connect to any database as long as it is permitted to execute with administrator's privileges.
- Execution of the present invention begins with the data analyzer (102) wherein the at least one data analyzer (102) is called to perform database analysis to produce draft of database structure. Thereafter, the other component of the system; the relationship builder (104) confine the database structure and convert the draft database structure to a confirm structure.
- the remaining component of the system; the data transformer (106) will automatically transform and realize the structures and thereafter export data from source to target. The details of the function of each of the components will be described in detail together with the methodology of the present invention.
- the methodology of the present invention for automatic transformation of non-relational database into relational database is first executed by initializing configuration of transformation process (202) wherein policy setup and administration state is being configured. Thereafter, the at least one data analyzer (102) performs database analysis by analyzing non-relational database and data structure to form database tree (204).
- the relationship builder (104) confine the database structure and convert the draft database structure to a confirm structure by identifying relationship and key and further associating it with database tree to form draft database structure (206); and evaluating relationship binding to produce confine database structure (208).
- the at least one data transformer (106) creates database by constructing database, tables and relationship into relational database (210); and data insertion is performed with key identification and valid data format for database transformation (212).
- the said non-relational database is in DBMS (Database Management System) format and relational database is in RDBMS (Relational Database Management System) format.
- FIG. 3.0 is a flowchart illustrating the method for analyzing non-relational database and data structure to form database tree.
- the at least one data analyzer (102) starts analyzing non-relational database and data structure to form database tree by reading non-relational database to search for DBMS file (302) and accordingly extracts table structure from at least one identified DBMS file (304).
- the said method continues with source code analysis using Al (Abstract Interpretation) to locate complete table structures (306) wherein the complete table structures may include field size, type and format.
- AST Abstract Syntax Tree
- database tree will be generated with extracted table structure obtained from at least one identified DBMS file and table structure obtained from analysis of source code (308).
- FIG. 4.0 is a flowchart illustrating the method for identifying relationship and key and further associating it with database tree to form draft database structure.
- the methodology for automatic transformation of non-relational database into relational database continues with identifying relationship and key and further associating it with database tree to form draft database structure.
- the said method starts by constructing and loading AST into database tree (402) and continues by analyzing at least one identified DBMS file identified in (step 302) with LA (Lexical Analysis) to obtain table references and key (404). Thereafter, at least one reference and at least one key is generated based on results obtained through LA in (step 404) (406).
- a plurality of keys with identical names with different format, type and length may be generated during the process of key generation based on results obtained through LA in (step 404).
- the at least one reference and the at least one key will be tagged to generated database tree to form draft database structure (408).
- FIG. 5.0 is a flowchart illustrating the method for evaluating relationship binding to produce confine database structure.
- evaluation and binding of relationship is performed to produce a confine database structure.
- the system will first read and load at least one DBMS file into memory (502). Thereafter, flow analysis is performed on results obtained through LA in (step 404, 406) using DFA (Data Flow Analysis) to obtain data flow, relationship and field format (504).
- DFA Data Flow Analysis
- the method continues with relationship binding with AST generated in (step 308) and database tree generated from DFA in (step 504) (506). Unwanted keys or relations are removed during relationship binding. Subsequently, table structures are synchronized and aligned to produce a confine database structure (508).
- FIG. 6.0 is a flowchart illustrating the method for creating database by constructing database, tables and relationship into relational database.
- creation of database starts by generating database scripts from generated AST (602). Keys based on AST will be generated (604) and the database scripts will be added with said key generation scripts.
- relationship generation script will be generated based on DFA and AST (606) and database creation will be executed based on complete and structured table (608).
- data insertion is performed with key identification and valid data format for database transformation wherein data transformer transform and realize the structure and export data from source to target.
- the present invention provides a system and method for automatic transformation of non- related data into RDBMS format wherein the present invention automatically creates relationship between data structures in a system whereby there is no existence of relationship during transformation; synchronize structures, type and format between unknown data structures for relationship binding between the data structures; and automatically creates table and data relationship and performing data transformation without or with minor intervention thus having a self- reliant transformation process with higher accuracy of data relationship.
- the distinctiveness of the present invention lies in the techniques of relationship generation using Abstract Interpretation (Al), Lexical Analysis and Data Flow Analysis for automatic transformation of non- related data into RDBMS format.
- the present invention may be embodied in other specific forms without departing from its essential characteristics.
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Automatic Analysis And Handling Materials Therefor (AREA)
Abstract
The system and method of the present invention provides for automatic transformation of non-relational database into relational database that is self-reliant. The system of the present invention comprising at least one data analyzer (102); at least one relationship builder (104); and at least one data transformer (106) for automatically transforming non-relational database into relational database. Execution of the present invention begins with the data analyzer (102) wherein the at least one data analyzer (102) is called to perform database analysis to produce draft of database structure. Thereafter, the other component of the system; the relationship builder (104) confine the database structure and convert the draft database structure to a confirm structure. Upon confirmation of the database structure, data transformer (106) will automatically transform and realize the structures and thereafter export data from source to target. In short, the methodology of the present invention comprising steps of initializing configuration of transformation process (202); analyzing non-relational database and data structure to form database tree (204); identifying relationship and key and further associating it with database tree to form draft database structure (206); evaluating relationship binding to produce confine database structure (208); creating database by constructing database, tables and relationship into relational database (210); and performing data insertion with key identification and valid data format for database transformation (212).
Description
AUTOMATIC TRANSFORMATION OF NON-RELATIONAL DATABASE INTO
RELATIONAL DATABASE
FIELD OF INVENTION
The present invention relates to a system and method for automatic transformation of nonrelational database into relational database that is self-reliant.
BACKGROUND ART
Legacy system contains unstructured data as there are different tables, files, or database which is using different format or structure. Data transformation in legacy system remains a hassle task as there is no existence of relationship between the data. In addition, the format of data is defined differently by users. Therefore, more time is required to synchronize data definition and error may occur during data transformation due to invalid definition. The database of legacy system may store corrupted data due to the wrongly defined data format.
The presently available data transformation system is time consuming in defining the data process, in data structure analysis and data transformation as it requires human intervention. Accuracy of the presently available system is low and thus requires more resources in amending the data. Hence, current solutions are yet to improve the level of trust for analysis and decision making. The present invention proposes a system and method that automatically creates relationship between data structures in a system whereby no relationship exist during transformation; to synchronize the structures, type and format between unknown data structures for relationship binding between the data structures and automatically create table and data relationship and perform data transformation without the need for human intervention thus having self-reliant transformation process with higher accuracy of data relationship.
The approach as proposed in the present invention performs automatic transformation of non-relational DBMS (Database Management System) to RDBMS (Relational DBMS)
whereby no relations or key is defined or declared. It consists of a method to perform database analysis on DBMS; mainly but not limited to non-relational DBMS and flat-file; using LA (Lexical Analysis) and Al (Abstract Interpretation). The proposed solution will then incorporate a method to identify and construct the relationship between non-relational data using DFA (Data Flow Analysis) techniques together with the result from the previous method. Finally, the solution will automatically create a database, correct and harmonize tables and its structure, and perform data insertion with accurate key identification with a valid data and format. The subject matter claimed herein is not limited to embodiments that solve any disadvantages or that operate only in environments such as those described above. Rather, this background is only provided to illustrate one exemplary technology area where some embodiments described herein may be practice.
SUMMARY OF INVENTION
The present invention provides a system and method for automatic transformation of nonrelational database into relational database that is self-reliant. One aspect of the present invention provides a system for automatic transformation of non-relational database into relational database that is self-reliant. The system comprising at least one data analyzer (102); at least one relationship builder (104); and at least one data transformer (106) for automatically transforming non- relational database into relational database. The at least one data analyzer (102) having means for analyzing non-relational database and data structure to form database tree while the at least one relationship builder (104) having means for identifying relationship and key and further associating it with database tree to form draft database structure; and evaluating relationship binding to produce confine database structure. One aspect of the present invention provides for the at least one data transformer (106) for automatically transforming non-relational database into relational database. The at least one data transformer (106) having means for creating database by constructing database, tables and relationship into relational database; and performing data insertion with key identification and valid data format for database transformation. The said non-relational database is in DBMS (Database Management System) format and relational database is in RDBMS (Relational Database Management System) format.
Preferably, the present invention provides a method (200) for automatic transformation of non-relational database into relational database that is self-reliant. The method comprising steps of initializing configuration of transformation process (202); analyzing non-relational database and data structure to form database tree (204); identifying relationship and key and further associating it with database tree to form draft database structure (206); evaluating relationship binding to produce confine database structure (208); creating database by constructing database, tables and relationship into relational database (210); and performing data insertion with key identification and valid data format for database transformation (212).
Another aspect of the present invention describes the further steps of the method for analyzing non-relational database and data structure to form database tree. The said
method further comprising steps of reading non-relational database to search for DBMS file (302); extracting table structure from at least one identified DBMS file (304); analyzing source code using Al (Abstract Interpretation) to locate complete table structures which may include field size, type and format (306); and generating AST (Abstract Syntax Tree) using extracted table structure obtained from at least one identified DBMS file and table structure obtained from analysis of source code (308).
Preferably, the present invention provides the further steps of the method for identifying relationship and key and further associating it with database tree to form draft database structure. The said method further comprising steps of constructing and loading AST into database tree (402); analyzing at least one identified DBMS file identified in (step 302) with LA (Lexical Analysis) to obtain table references and key (404); generating at least one reference and at least one key based on results obtained through LA in (step 404) wherein a plurality of keys with identical names with different format, type and length is generated; and tagging at least one reference and at least one key obtained to generated database tree to form draft database structure.
A further aspect of the present invention provides further steps of the method for evaluating relationship binding to produce confine database structure. The said method further comprising steps of reading and loading at least one DBMS file into memory (502); performing flow analysis on results obtained through LA in (step 404, 406) using DFA (Data Flow Analysis) to obtain data flow, relationship and field format (504); binding relationship with AST generated in (step 308) and database tree generated from DFA in (step 504) (506); and synchronizing and aligning table structure to produce a confine database structure (508).
Preferably, the present invention provides further steps for creating database by constructing database, tables and relationship into relational database. The said method further comprising steps of generating database scripts from generated AST (602); generating keys based on AST (604); generating relationship script based on DFA and AST (606); and executing database creation based on complete and structured table (608).
The present invention consists of features and a combination of parts hereinafter fully described and illustrated in the accompanying drawings, it being understood that various changes in the details may be made without departing from the scope of the invention or sacrificing any of the advantages of the present invention.
BRIEF DESCRIPTION OF ACCOMPANYING DRAWINGS
To further clarify various aspects of some embodiments of the present invention, a more particular description of the invention will be rendered by references to specific embodiments thereof, which are illustrated in the appended drawings. It is appreciated that these drawings depict only typical embodiments of the invention and are therefore not to be considered limiting of its scope. The invention will be described and explained with additional specificity and detail through the accompanying drawings in which: FIG. 1.0 illustrates the block diagram of the architecture of present invention in comparison with the architecture of the legacy system.
FIG. 2.0 is a flowchart illustrating the method for automatic-transformation of non-relational database into relational database that is self-reliant.
FIG. 3.0 is a flowchart illustrating the method for analyzing non-relational database and data structure to form database tree.
FIG. 4.0 is a flowchart illustrating the method for identifying relationship and key and further associating it with database tree to form draft database structure.
FIG. 5.0 is a flowchart illustrating the method for evaluating relationship binding to produce confine database structure. FIG. 6.0 is a flowchart illustrating the method for creating database by constructing database, tables and relationship into relational database.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
The present invention provides a system and method for automatic transformation of nonrelational database into relational database that is self-reliant. Hereinafter, this specification will describe the present invention according to the preferred embodiments. It is to be understood that limiting the description to the preferred embodiments of the invention is merely to facilitate discussion of the present invention and it is envisioned without departing from the scope of the appended claims. Reference is first being made to FIG. 1.0 and FIG. 2.0 respectively. FIG. 1.0 illustrates the block diagram of the architecture of present invention in comparison with the architecture of the legacy system and FIG. 2.0 is a flowchart illustrating the method for automatic- transformation of non-relational database into relational database that is self-reliant. As illustrated in FIG. 1.0, the system of the present invention comprising at least one data analyzer (102); at least one relationship builder (104); and at least one data transformer (106) for automatically transforming non-relational database into relational database. The present invention is applicable in any database transformation and in any environment provided that the source and target are available and accessible by the solution. The system as proposed in the present invention can be invoked from any defined host and connect to any database as long as it is permitted to execute with administrator's privileges. Execution of the present invention begins with the data analyzer (102) wherein the at least one data analyzer (102) is called to perform database analysis to produce draft of database structure. Thereafter, the other component of the system; the relationship builder (104) confine the database structure and convert the draft database structure to a confirm structure. Upon confirmation of the database structure, the remaining component of the system; the data transformer (106) will automatically transform and realize the structures and thereafter export data from source to target. The details of the function of each of the components will be described in detail together with the methodology of the present invention.
As illustrated in FIG. 2.0, the methodology of the present invention for automatic transformation of non-relational database into relational database is first executed by initializing configuration of transformation process (202) wherein policy setup and administration state is being configured. Thereafter, the at least one data analyzer (102)
performs database analysis by analyzing non-relational database and data structure to form database tree (204). The relationship builder (104) confine the database structure and convert the draft database structure to a confirm structure by identifying relationship and key and further associating it with database tree to form draft database structure (206); and evaluating relationship binding to produce confine database structure (208). Subsequently, the at least one data transformer (106) creates database by constructing database, tables and relationship into relational database (210); and data insertion is performed with key identification and valid data format for database transformation (212). The said non-relational database is in DBMS (Database Management System) format and relational database is in RDBMS (Relational Database Management System) format.
Reference is now being made to FIG. 3.0. FIG. 3.0 is a flowchart illustrating the method for analyzing non-relational database and data structure to form database tree. As illustrated in FIG. 3.0, the at least one data analyzer (102) starts analyzing non-relational database and data structure to form database tree by reading non-relational database to search for DBMS file (302) and accordingly extracts table structure from at least one identified DBMS file (304). The said method continues with source code analysis using Al (Abstract Interpretation) to locate complete table structures (306) wherein the complete table structures may include field size, type and format. Thereafter, AST (Abstract Syntax Tree) or database tree will be generated with extracted table structure obtained from at least one identified DBMS file and table structure obtained from analysis of source code (308).
Reference is now being made to FIG. 4.0. FIG. 4.0 is a flowchart illustrating the method for identifying relationship and key and further associating it with database tree to form draft database structure. Upon completion of database analysis by the data analyzer, the methodology for automatic transformation of non-relational database into relational database continues with identifying relationship and key and further associating it with database tree to form draft database structure. The said method starts by constructing and loading AST into database tree (402) and continues by analyzing at least one identified DBMS file identified in (step 302) with LA (Lexical Analysis) to obtain table references and key (404). Thereafter, at least one reference and at least one key is generated based on results obtained through LA in (step 404) (406). A plurality of keys with identical names with different format, type and length may be generated during the process of key generation based on results obtained through LA in (step 404). Upon generating at least
one reference and at least one key, the at least one reference and the at least one key will be tagged to generated database tree to form draft database structure (408).
Reference is now being made to FIG. 5.0. FIG. 5.0 is a flowchart illustrating the method for evaluating relationship binding to produce confine database structure. Upon completion of creation of draft database structure, evaluation and binding of relationship is performed to produce a confine database structure. As illustrated in FIG. 5.0, the system will first read and load at least one DBMS file into memory (502). Thereafter, flow analysis is performed on results obtained through LA in (step 404, 406) using DFA (Data Flow Analysis) to obtain data flow, relationship and field format (504). The method continues with relationship binding with AST generated in (step 308) and database tree generated from DFA in (step 504) (506). Unwanted keys or relations are removed during relationship binding. Subsequently, table structures are synchronized and aligned to produce a confine database structure (508).
Reference is now being made to FIG. 6.0. FIG. 6.0 is a flowchart illustrating the method for creating database by constructing database, tables and relationship into relational database. As illustrated in FIG. 6.0, creation of database starts by generating database scripts from generated AST (602). Keys based on AST will be generated (604) and the database scripts will be added with said key generation scripts. Once completed, relationship generation script will be generated based on DFA and AST (606) and database creation will be executed based on complete and structured table (608). Upon creation of said database, data insertion is performed with key identification and valid data format for database transformation wherein data transformer transform and realize the structure and export data from source to target.
As described and illustrated in the relevant figures, the present invention provides a system and method for automatic transformation of non- related data into RDBMS format wherein the present invention automatically creates relationship between data structures in a system whereby there is no existence of relationship during transformation; synchronize structures, type and format between unknown data structures for relationship binding between the data structures; and automatically creates table and data relationship and performing data transformation without or with minor intervention thus having a self- reliant transformation process with higher accuracy of data relationship. The
distinctiveness of the present invention lies in the techniques of relationship generation using Abstract Interpretation (Al), Lexical Analysis and Data Flow Analysis for automatic transformation of non- related data into RDBMS format. The present invention may be embodied in other specific forms without departing from its essential characteristics. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is, therefore indicated by the appended claims rather than by the foregoing description. All changes, which come within the meaning and range of equivalency of the claims, are to be embraced within their scope.
Claims
A system (100) for automatic transformation of non-relational database into relational database that is self-reliant, the system comprising:
at least one data analyzer (102) having means for analyzing non- relational database and data structure to form database tree;
at least one relationship builder (104) having means for identifying relationship and key and further associating it with database tree to form draft database structure; and evaluating relationship binding to produce confine database structure; and
at least one data transformer (106) for automatically transforming nonrelational database into relational database having means for creating database by constructing database, tables and relationship into relational database; and performing data insertion with key identification and valid data format for database transformation
characterized in that
the at least one data analyzer (102) having means for analyzing nonrelational database and data structure to form database tree further having means for:
reading non-relational database to search for DBMS file (302);
extracting table structure from at least one identified DBMS file
(304);
analyzing source code using Al (Abstract Interpretation) to locate complete table structures (306); and
generating AST (Abstract Syntax Tree) using extracted table structure obtained from at least one identified DBMS file and table structure obtained from analysis of source code (308). A system according to Claim 1 , wherein said non-relational database is in DBMS (Database Management System) format and relational database is in RDBMS (Relational Database Management System) format.
A method (200) for automatic transformation of non-relational database into relational database that is self-reliant; the method comprising steps of:
initializing configuration of transformation process (202);
analyzing non-relational database and data structure to form database tree (204);
identifying relationship and key and further associating it with database tree to form draft database structure (206);
evaluating relationship binding to produce confine database structure (208);
creating database by constructing database, tables and relationship into relational database (210); and
performing data insertion with key identification and valid data format for database transformation (212)
characterized in that
analyzing non-relational database and data structure to form database tree (204) further comprises steps of:
reading non-relational database to search for DBMS file (302);
extracting table structure from at least one identified DBMS file
(304);
analyzing source code using Al (Abstract Interpretation) to locate complete table structures (306); and
generating AST (Abstract Syntax Tree) using extracted table structure obtained from at least one identified DBMS file and table structure obtained from analysis of source code
(308).
A method according to Claim 3, wherein complete table structures include field size, type and format.
A method according to Claim 3, wherein identifying relationship and key and further associating it with database tree to form draft database structure further comprising steps of:
constructing and loading AST into database tree (402);
analyzing at least one identified DBMS file identified in (step 302) with LA (Lexical Analysis) to obtain table references and key (404);
generating at least one reference and at least one key based on results obtained through LA in (step 404) (406); and
tagging at least one reference and at least one key obtained to generated database tree to form draft database structure (408).
6. A method according to Claim 5, wherein generating at least one reference and at least one key based on results obtained through LA in (step 404) further comprising generating a plurality of keys with identical names with different format, type and length.
7. A method according to Claim 3, wherein evaluating relationship binding to produce confine database structure further comprising steps of:
reading and loading at least one DBMS file into memory (502); performing flow analysis on results obtained through LA in (step 404, 406) using DFA (Data Flow Analysis) to obtain data flow, relationship and field format (504);
binding relationship with AST generated in (step 308) and database tree generated from DFA in (step 504) (506); and
synchronizing and aligning table structure to produce a confine database structure (508).
8. A method according to Claim 3, wherein creating database by constructing database, tables and relationship into relational database further comprising steps of:
generating database scripts from generated AST (602);
generating keys based on AST (604);
generating relationship script based on DFA and AST (606); and executing database creation based on complete and structured table (608).
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
MYPI2012005266 | 2012-12-05 | ||
MYPI2012005266A MY166591A (en) | 2012-12-05 | 2012-12-05 | Automatic transformation of non-relational database into relational database |
Publications (2)
Publication Number | Publication Date |
---|---|
WO2014088396A2 true WO2014088396A2 (en) | 2014-06-12 |
WO2014088396A3 WO2014088396A3 (en) | 2014-07-24 |
Family
ID=50029181
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/MY2013/000216 WO2014088396A2 (en) | 2012-12-05 | 2013-11-29 | Automatic transformation of non-relational database into relational database |
Country Status (2)
Country | Link |
---|---|
MY (1) | MY166591A (en) |
WO (1) | WO2014088396A2 (en) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN105938479A (en) * | 2016-03-31 | 2016-09-14 | 华南师范大学 | Structural transfer method of relational tables and non-relational tables |
CN108664505A (en) * | 2017-03-30 | 2018-10-16 | 腾讯科技(深圳)有限公司 | A kind of deriving method and device of database table structure |
CN111506642A (en) * | 2020-06-12 | 2020-08-07 | 夸克云智科技(深圳)有限公司 | Data conversion method based on basic data type |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6631382B1 (en) * | 1996-01-02 | 2003-10-07 | Timeline, Inc. | Data retrieval method and apparatus with multiple source capability |
-
2012
- 2012-12-05 MY MYPI2012005266A patent/MY166591A/en unknown
-
2013
- 2013-11-29 WO PCT/MY2013/000216 patent/WO2014088396A2/en active Application Filing
Non-Patent Citations (1)
Title |
---|
None |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN105938479A (en) * | 2016-03-31 | 2016-09-14 | 华南师范大学 | Structural transfer method of relational tables and non-relational tables |
CN105938479B (en) * | 2016-03-31 | 2019-10-22 | 华南师范大学 | A kind of structure conversion method of relation table and non-relation table |
CN108664505A (en) * | 2017-03-30 | 2018-10-16 | 腾讯科技(深圳)有限公司 | A kind of deriving method and device of database table structure |
CN108664505B (en) * | 2017-03-30 | 2021-08-13 | 腾讯科技(深圳)有限公司 | Method and device for exporting database table structure |
CN111506642A (en) * | 2020-06-12 | 2020-08-07 | 夸克云智科技(深圳)有限公司 | Data conversion method based on basic data type |
Also Published As
Publication number | Publication date |
---|---|
WO2014088396A3 (en) | 2014-07-24 |
MY166591A (en) | 2018-07-17 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP2019114240A (en) | Data duplication for heterogeneous database via sql packet analysis and synchronization error detection method and system | |
CN102737020B (en) | Method for initializing multi-tenant database, and apparatus thereof | |
WO2016026328A1 (en) | Information processing method and device and computer storage medium | |
CN105320681B (en) | Database content merging method and device | |
US10360002B2 (en) | Method, apparatus, and computer-readable medium for generating an alternative implementation of a program on one or more engines | |
CN106843840A (en) | A kind of version evolving annotation multiplexing method of source code based on similarity analysis | |
CN103377123B (en) | A kind of web page code automated testing method and device | |
WO2015097789A1 (en) | Query generating method and query generating device | |
CN104899141A (en) | Test case selecting and expanding method facing network application system | |
CN109165209A (en) | The data verification method, device of object type, equipment and medium in database | |
CN116804994B (en) | Data synchronization method, system, device, electronic equipment and storage medium | |
Higo et al. | Enhancement of CRD-based clone tracking | |
CN108388606B (en) | Method for checking base table field names in Sql sentences and computer equipment | |
CN116560642A (en) | Code generation method and device, electronic equipment and storage medium | |
WO2014088396A2 (en) | Automatic transformation of non-relational database into relational database | |
CN106126224A (en) | Tool, system and method for generating program object | |
CN110990055A (en) | Pull Request function classification method based on program analysis | |
CN111813648A (en) | Automatic testing method and device applied to App, storage medium and electronic equipment | |
CN112567375A (en) | Format verification method, information identification method, device and storage medium | |
CN115292347A (en) | Active SQL algorithm performance checking device and method based on rules | |
US20150347402A1 (en) | System and method for enabling a client system to generate file system operations on a file system data set using a virtual namespace | |
Stacy et al. | Metamorphic testing in bioinformatics software: a case study on metagenomic assembly | |
CN115438341A (en) | Method and device for extracting code loop counter, storage medium and electronic equipment | |
CN110727726B (en) | Method and system for extracting data from document database to relational database | |
TW202217640A (en) | Method and system for labeling object and generating security policy in operating system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 13824672 Country of ref document: EP Kind code of ref document: A2 |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 13824672 Country of ref document: EP Kind code of ref document: A2 |