CN110597821A - Method and device for changing database table structure - Google Patents
Method and device for changing database table structure Download PDFInfo
- Publication number
- CN110597821A CN110597821A CN201910890691.XA CN201910890691A CN110597821A CN 110597821 A CN110597821 A CN 110597821A CN 201910890691 A CN201910890691 A CN 201910890691A CN 110597821 A CN110597821 A CN 110597821A
- Authority
- CN
- China
- Prior art keywords
- data
- field
- program
- umd
- data table
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
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/22—Indexing; Data structures therefor; Storage structures
- G06F16/2282—Tablespace storage structures; Management thereof
Abstract
The application discloses a method and a device for changing a database table structure, wherein the method comprises the following steps: comparing the ODS layer table structure with a table structure defined in an upstream system data dictionary, and determining a data table with a changed table structure as a first data table; generating a table deleting program according to the table name of the first data table and a preset table deleting program template, and deleting the first data table by using the table deleting program; generating a table building program according to the table name and the field attribute of the first data table and a preset table building program template, and rebuilding the first data table by using the table building program to obtain a second data table; comparing the fields in the UMD layer full data table corresponding to the second data table with the fields in the second data table to determine the changed fields in the UMD layer full data table; and generating a changing program according to the field attribute of the changed field and a preset field changing program template, and changing the field in the UMD layer full data sheet by using the field changing program. The method and the device can automatically modify the table structure in the data warehouse.
Description
Technical Field
The application relates to the technical field of data warehouses, in particular to a method and a device for changing a database table structure of a data warehouse.
Background
This section is intended to provide a background or context to the embodiments of the invention that are recited in the claims. The description herein is not admitted to be prior art by inclusion in this section.
After receiving Data files sent by an upstream system every day, a Data warehouse system loads the Data files into an Operational Data Storage (ODS) layer Data table, and then the Data table is processed into a Unified Data Manager (UDM) layer Data table through a process of storing full Data. If the table structure of the upstream system is changed, the table structures of the ODS layer and the UMD layer in the data warehouse are changed accordingly.
At present, a maintainer generally compares an ODS table structure in a current data warehouse with a table structure defined in an upstream system data dictionary to find added or deleted modified fields, and then writes an ODS layer table structure modification program and a UDM layer table processing logic item by item, and modifies the table structure in the data warehouse by using the ODS layer table structure modification program and the UDM layer table processing logic item. For a data warehouse with a huge number of related data tables, a great deal of time and energy are needed for maintenance personnel to perform manual modification every time, and meanwhile, the error rate is high and the modification efficiency is low.
Disclosure of Invention
The embodiment of the application provides a method for changing a database table structure of a data warehouse, which is used for automatically modifying the table structure in the data warehouse, saving manpower, improving modification efficiency and reducing error rate, and comprises the following steps:
comparing the ODS layer table structure with a table structure defined in an upstream system data dictionary, and determining a data table with a changed table structure as a first data table; generating a table deleting program according to the table name of the first data table and a preset table deleting program template, and deleting the first data table by using the table deleting program; generating a table building program according to the table name and the field attribute of the first data table and a preset table building program template, and rebuilding the first data table by using the table building program to obtain a second data table; comparing the fields in the UMD layer full data table corresponding to the second data table with the fields in the second data table to determine the changed fields in the UMD layer full data table; and generating a change program according to the field attribute of the change field and a preset field change program template, and changing the field in the UMD layer full data sheet by using the change program.
The embodiment of this application still provides a data warehouse table structure change device for the table structure in the automatic modification data warehouse practices thrift the manpower, improves and revises efficiency, reduces the error rate, and the device includes:
a comparison module, which is used for comparing the ODS layer table structure with the table structure defined in the upstream system data dictionary, and determining the data table with the changed table structure as a first data table; the table deleting module is used for generating a table deleting program according to the table name of the first data table determined by the comparing module and a preset table deleting program template, and deleting the first data table by using the table deleting program; the table building module is used for generating a table building program according to the table name and the field attribute of the first data table determined by the comparison module and a preset table building program template, and rebuilding the first data table by using the table building program to obtain a second data table; the comparison module is also used for comparing the fields in the UMD layer full data table corresponding to the second data table established by the table establishing module with the fields in the second data table to determine the changed fields in the UMD layer full data table; and the field changing module is used for generating a changing program according to the field attribute of the changed field determined by the comparing module and a preset field changing program template, and changing the field in the UMD layer full data sheet by using the field changing program.
In the embodiment of the application, the preset table building program template, the table deleting program template and the field are changed into the program template to generate the automatic processing programs such as the table building program, the table deleting program and the field changing program, the automatic processing programs delete and rebuild the ODS layer data table and change the fields in the UMD layer full data table to complete the synchronous change of the ODS layer and the UMD layer of the data warehouse caused by the change of the table structure of the upstream system, the changing process is automatically carried out without human participation, the time and the energy consumed by maintenance personnel for manually changing the data are saved, the error rate of coding is reduced, and the changing efficiency is improved.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts. In the drawings:
fig. 1 is a flowchart of a method for changing a database table structure in an embodiment of the present application;
fig. 2 is a schematic structural diagram of a data warehouse table structure changing device in an embodiment of the present application.
Detailed Description
To make the objects, technical solutions and advantages of the embodiments of the present application more apparent, the embodiments of the present application are further described in detail below with reference to the accompanying drawings. The exemplary embodiments and descriptions of the present application are provided herein to explain the present application and not to limit the present application.
An embodiment of the present application provides a method for changing a database table structure, as shown in fig. 1, the method includes steps 101 to 105:
step 101, comparing the ODS layer table structure with the table structure defined in the upstream system data dictionary, and determining the data table with the changed table structure as the first data table.
The data dictionary is used for describing the structure of the data file issued by the upstream system, and records the information of the table in the upstream system database, including the information of the table name, the field type, the field length and the like.
The table structure in the data warehouse is consistent with that in the upstream system, and the table structure in the upstream system is defined in the data dictionary, so that the data table with the changed table structure in the data warehouse can be determined by comparing the table structure in the data warehouse with that defined in the data dictionary of the upstream system.
And 102, generating a table deleting program according to the table name of the first data table and a preset table deleting program template, and deleting the first data table by using the table deleting program.
And 103, generating a table building program according to the table name and the field attribute of the first data table and a preset table building program template, and rebuilding the first data table by using the table building program to obtain a second data table.
Wherein the field attribute comprises a field name, a field type, a field length and a field number.
Because only current date data is stored in the ODS layer data table, and full data is stored in the UDM layer full data table, the ODS layer data is emptied to avoid duplication before writing data files sent by an upstream system into the UDM layer full data table each time. Therefore, if the table structure in the upstream system is changed, the fields in the ODS layer data table do not need to be modified, and only the original ODS layer data table needs to be deleted, and the ODS layer data table is established again according to the table structure of the upstream system.
And step 104, comparing the fields in the UMD layer full data table corresponding to the second data table with the fields in the second data table, and determining the changed fields in the UMD layer full data table.
The UMD layer full data table stores all data issued by an upstream system, the table reconstruction cannot be deleted as an ODS layer data table, and when the table structure of the upstream system is changed, the changed fields in the UMD layer full data table need to be modified in a targeted manner.
And 105, generating a change program according to the field attribute of the changed field and a preset field change program template, and changing the field in the UMD data table by using the change program.
In the embodiment of the present application, a changing program is generated according to a field attribute of a changed field and a preset field changing program template, and the field in the UMD data table is changed by using the changing program, including the following steps: judging the change type of the changed field, wherein the change type comprises modification, new addition or deletion; if the change type is modification, generating a modified field program according to the field attribute of the changed field and a preset modified field program template, and modifying the field in the UMD data table by using the modified field program; and if the change type is newly increased, generating a newly increased field program according to the field attribute of the change field and a preset newly increased field program template, and adding fields into the UMD data table by using the newly increased field program.
It should be noted that, compared with the ODS layer data table, if the number and name of the fields are consistent, but the field type and the field length are not consistent, the full-size data table of the UMD layer determines that the change type of the changed field is "modified"; if a field exists in the ODS layer data table and the UMD layer full data table does not have the field, judging the change type of the change field to be 'new'; if there is a case where the ODS layer data table does not have a field and the UMD layer full data table has the field, the change type of the changed field is judged to be "deleted".
In the embodiment of the present application, if the change type is deletion, all fields in the current UMD data table are reserved. That is, if a field is not included in the ODS layer data table and the field is included in the UDM layer full data table, the field is not deleted in the UDM layer full data table according to the "big-full" processing principle, and the field is reserved for the historical state record of the complete data table to be queried in the subsequent process.
After the table structures of the ODS layer data table and the UDM layer full data table in the data warehouse are changed, if the data warehouse receives a new data file issued by an upstream system, the table data type of each data table in the data file can be determined one by one according to the mapping relation between the preset table name and the data type; and writing the data in the data file into the UMD layer data table by using the UMD layer data adding method program corresponding to the data type of the table. The table data type comprises customer account data, transaction data or code table data.
The data types of the data stored in one data table are the same. Illustratively, names of data tables included in the data warehouse are an a table, a B table, a C table and a D table, and according to a mapping relation between the table names and the data types, it can be determined that the data type of the data in the a table is guest account type data, the data type of the data in the B table is code table type data, the data type of the data in the C table is transaction type data, and the data type of the data in the D table is code table type data.
The data of different data types are stored differently. The data tables of the guest account data and the code table data retain full data of the latest time point, and historical state data of the data are not retained, so that the two types of data add data issued by an upstream system into the UMD layer data table by adopting a merge method program; and the transaction data needs to keep all historical transaction data, so the data sent by an upstream system is added into the UMD layer data table by adopting an insert method program.
In addition, besides the three data types, other data types may also exist, and the method for writing the data types into the UMD layer full data table can be determined by analyzing according to specific data, and the corresponding relation between the method program and the data types is preset in the data warehouse. And when the data warehouse receives the data of the corresponding type, writing the data into the UMD layer full data table by using a preset method program.
In the embodiment of the application, the preset table building program template, the table deleting program template and the field are changed into the program template to generate the automatic processing programs such as the table building program, the table deleting program and the field changing program, the automatic processing programs delete and rebuild the ODS layer data table and change the fields in the UMD layer full data table to complete the synchronous change of the ODS layer and the UMD layer of the data warehouse caused by the change of the table structure of the upstream system, the changing process is automatically carried out without human participation, the time and the energy consumed by maintenance personnel for manually changing the data are saved, the error rate of coding is reduced, and the changing efficiency is improved.
The embodiment of the present application further provides a device for changing a database table structure, as shown in fig. 2, the device 200 includes a comparing module 201, a table deleting module 202, a table building module 203, and a field changing module 204.
Wherein, the comparing module 201 is configured to compare the ODS layer table structure with the table structure defined in the upstream system data dictionary, and determine the data table with the changed table structure as the first data table.
A table deleting module 202, configured to generate a table deleting program according to the table name of the first data table determined by the comparing module 201 and a preset table deleting program template, and delete the first data table by using the table deleting program.
The table building module 203 is configured to generate a table building program according to the table name and the field attribute of the first data table determined by the comparing module 201 and a preset table building program template, and reconstruct the first data table by using the table building program to obtain a second data table.
The comparing module 201 is further configured to compare fields in the UMD layer full data table corresponding to the second data table established by the table establishing module 203 with fields in the second data table, and determine changed fields in the UMD layer full data table.
And a field changing module 204, configured to generate a changing program according to the field attribute of the changed field determined by the comparing module 201 and a preset field changing program template, and change the field in the UMD layer full-size data table by using the field changing program.
In an implementation manner of the embodiment of the present application, the field changing module 204 is configured to:
judging the change type of the changed field, wherein the change type comprises modification, new addition or deletion;
if the change type is modification, generating a modified field program according to the field attribute of the changed field and a preset modified field program template, and modifying the field in the UMD layer full data table by using the modified field program;
and if the change type is newly increased, generating a newly increased field program according to the field attribute of the changed field and a preset newly increased field program template, and adding fields into the UMD layer full data sheet by using the newly increased field program.
In an implementation manner of the embodiment of the present application, if the change type is deletion, all fields in the current UMD layer full data table are reserved.
In one implementation manner of the embodiment of the present application, the apparatus 200 further includes:
the determining module 205 is configured to determine, when a data file sent by an upstream system is received, a table data type of each data table in the data file one by one according to a mapping relationship between a preset table name and the data type, where the table data type includes customer account data, transaction data, or code table data.
A data writing module 206, configured to write data in the data file into the UMD layer full data table by using the UMD layer data adding method program corresponding to the table data type determined by the determining module 205.
In an implementation manner of the embodiment of the present application, the UMD layer data adding method program corresponding to the guest account type data and the code table type data is a merge method program. And the UMD layer data adding method program corresponding to the transaction data is an insert method program.
In the embodiment of the application, the preset table building program template, the table deleting program template and the field are changed into the program template to generate the automatic processing programs such as the table building program, the table deleting program and the field changing program, the automatic processing programs delete and rebuild the ODS layer data table and change the fields in the UMD layer full data table to complete the synchronous change of the ODS layer and the UMD layer of the data warehouse caused by the change of the table structure of the upstream system, the changing process is automatically carried out without human participation, the time and the energy consumed by maintenance personnel for manually changing the data are saved, the error rate of coding is reduced, and the changing efficiency is improved.
The embodiment of the present application provides a computer device, which includes a memory, a processor, and a computer program stored on the memory and executable on the processor, and the processor implements the method described in any one of steps 101 to 105 and various implementation manners thereof when executing the computer program.
A computer-readable storage medium is provided in an embodiment of the present application, and stores a computer program for executing the method described in any one of steps 101 to 105 and various implementation manners thereof.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The above-mentioned embodiments are further described in detail for the purpose of illustrating the invention, and it should be understood that the above-mentioned embodiments are only illustrative of the present invention and are not intended to limit the scope of the present invention, and any modifications, equivalent substitutions, improvements, etc. made within the spirit and principle of the present invention should be included in the scope of the present invention.
Claims (10)
1. A method for changing a database table structure, the method comprising:
comparing the ODS layer table structure with a table structure defined in an upstream system data dictionary, and determining a data table with a changed table structure as a first data table;
generating a table deleting program according to the table name of the first data table and a preset table deleting program template, and deleting the first data table by using the table deleting program;
generating a table building program according to the table name and the field attribute of the first data table and a preset table building program template, and rebuilding the first data table by using the table building program to obtain a second data table;
comparing the fields in the UMD layer full data table corresponding to the second data table with the fields in the second data table to determine the changed fields in the UMD layer full data table;
and generating a changing program according to the field attribute of the changed field and a preset field changing program template, and changing the field in the UMD layer full data sheet by using the field changing program.
2. The method of claim 1, wherein generating a change program according to the field attribute of the changed field and a preset field change program template, and changing the field in the full-size data table of the UMD layer by using the change program comprises:
judging the change type of the change field, wherein the change type comprises modification, new addition or deletion;
if the change type is modification, generating a modified field program according to the field attribute of the changed field and a preset modified field program template, and modifying the field in the UMD layer full data table by using the modified field program;
and if the change type is newly increased, generating a newly increased field program according to the field attribute of the changed field and a preset newly increased field program template, and adding fields into the UMD layer full data sheet by using the newly increased field program.
3. The method of claim 2, wherein if the change type is delete, then retaining all fields in the current UMD layer full data table.
4. The method as claimed in claim 1, wherein after altering the fields in the UMD layer full size data table using an altering program, the method further comprises:
when a data file issued by an upstream system is received, determining the table data type of each data table in the data file one by one according to the mapping relation between the preset table name and the data type, wherein the table data type comprises customer account data, transaction data or code table data;
and writing the data in the data file into the UMD layer full data table by using a UMD layer data adding method program corresponding to the data type of the table.
5. The method of claim 4,
the UMD layer data adding method program corresponding to the guest account data and the code table data is a merge method program;
and the UMD layer data adding method program corresponding to the transaction data is an insert method program.
6. An apparatus for changing a structure of a database table, the apparatus comprising:
a comparison module, which is used for comparing the ODS layer table structure with the table structure defined in the upstream system data dictionary, and determining the data table with the changed table structure as a first data table;
the table deleting module is used for generating a table deleting program according to the table name of the first data table determined by the comparing module and a preset table deleting program template, and deleting the first data table by using the table deleting program;
the table building module is used for generating a table building program according to the table name and the field attribute of the first data table determined by the comparison module and a preset table building program template, and rebuilding the first data table by using the table building program to obtain a second data table;
the comparison module is also used for comparing the fields in the UMD layer full data table corresponding to the second data table established by the table establishing module with the fields in the second data table to determine the changed fields in the UMD layer full data table;
and the field changing module is used for generating a changing program according to the field attribute of the changed field determined by the comparing module and a preset field changing program template, and changing the field in the UMD layer full data sheet by using the field changing program.
7. The apparatus of claim 6, wherein the field change module is configured to:
judging the change type of the change field, wherein the change type comprises modification, new addition or deletion;
if the change type is modification, generating a modified field program according to the field attribute of the changed field and a preset modified field program template, and modifying the field in the UMD layer full data table by using the modified field program;
and if the change type is newly increased, generating a newly increased field program according to the field attribute of the changed field and a preset newly increased field program template, and adding fields into the UMD layer full data sheet by using the newly increased field program.
8. The apparatus of claim 6, further comprising:
the determining module is used for determining the table data type of each data table in the data file one by one according to the mapping relation between the preset table name and the data type when the data file sent by an upstream system is received, wherein the table data type comprises customer account data, transaction data or code table data;
and the data writing module is used for writing the data in the data file into the UMD layer full data table by using the UMD layer data adding method program corresponding to the table data type determined by the determining module.
9. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the method of any one of claims 1 to 5 when executing the computer program.
10. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program for executing the method of any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910890691.XA CN110597821B (en) | 2019-09-20 | 2019-09-20 | Method and device for changing database table structure |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910890691.XA CN110597821B (en) | 2019-09-20 | 2019-09-20 | Method and device for changing database table structure |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110597821A true CN110597821A (en) | 2019-12-20 |
| CN110597821B CN110597821B (en) | 2022-05-17 |
Family
ID=68861679
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910890691.XA Active CN110597821B (en) | 2019-09-20 | 2019-09-20 | Method and device for changing database table structure |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110597821B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115878631A (en) * | 2023-02-03 | 2023-03-31 | 北京智芯微电子科技有限公司 | Method and device for changing table structure of database table |
| CN117349359A (en) * | 2023-12-06 | 2024-01-05 | 成都数据集团股份有限公司 | Multi-source heterogeneous database import and export method and system |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| DE10349595B3 (en) * | 2003-10-24 | 2004-12-09 | Hyperstone Ag | Writing sectors of block-deletable memory, writes to alternative memory block sectors in sequence, storing their positions in sector table |
| US6934749B1 (en) * | 2000-05-20 | 2005-08-23 | Ciena Corporation | Tracking distributed data retrieval in a network device |
| CN103514223A (en) * | 2012-06-28 | 2014-01-15 | 阿里巴巴集团控股有限公司 | Data synchronism method and system of database |
| CN104199955A (en) * | 2014-09-15 | 2014-12-10 | 中国银行股份有限公司 | Information management system and information management method |
| CN105224527A (en) * | 2014-05-27 | 2016-01-06 | 北京宸瑞科技有限公司 | Be applicable to the general ETL method of multiple object table update mode |
| CN107895018A (en) * | 2017-11-15 | 2018-04-10 | 广州视睿电子科技有限公司 | Database update SQL generation methods, system, storage medium and computer equipment |
-
2019
- 2019-09-20 CN CN201910890691.XA patent/CN110597821B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6934749B1 (en) * | 2000-05-20 | 2005-08-23 | Ciena Corporation | Tracking distributed data retrieval in a network device |
| DE10349595B3 (en) * | 2003-10-24 | 2004-12-09 | Hyperstone Ag | Writing sectors of block-deletable memory, writes to alternative memory block sectors in sequence, storing their positions in sector table |
| CN103514223A (en) * | 2012-06-28 | 2014-01-15 | 阿里巴巴集团控股有限公司 | Data synchronism method and system of database |
| CN105224527A (en) * | 2014-05-27 | 2016-01-06 | 北京宸瑞科技有限公司 | Be applicable to the general ETL method of multiple object table update mode |
| CN104199955A (en) * | 2014-09-15 | 2014-12-10 | 中国银行股份有限公司 | Information management system and information management method |
| CN107895018A (en) * | 2017-11-15 | 2018-04-10 | 广州视睿电子科技有限公司 | Database update SQL generation methods, system, storage medium and computer equipment |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115878631A (en) * | 2023-02-03 | 2023-03-31 | 北京智芯微电子科技有限公司 | Method and device for changing table structure of database table |
| CN117349359A (en) * | 2023-12-06 | 2024-01-05 | 成都数据集团股份有限公司 | Multi-source heterogeneous database import and export method and system |
| CN117349359B (en) * | 2023-12-06 | 2024-02-20 | 成都数据集团股份有限公司 | Multi-source heterogeneous database import and export method and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110597821B (en) | 2022-05-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109271450B (en) | Database synchronization method, device, server and storage medium | |
| Karnitis et al. | Migration of relational database to document-oriented database: Structure denormalization and data transformation | |
| CN110209728B (en) | Distributed heterogeneous database synchronization method, electronic equipment and storage medium | |
| CN109448100B (en) | Three-dimensional model format conversion method, system, computer device and storage medium | |
| CN106933703B (en) | Database data backup method and device and electronic equipment | |
| CN104423960A (en) | Continuous project integration method and continuous project integration system | |
| CN111444196B (en) | Method, device and equipment for generating Hash of global state in block chain type account book | |
| CN103995854A (en) | Equipment cross-version upgrading method and device | |
| CN106933823B (en) | Data synchronization method and device | |
| CN108280137B (en) | Task-based pipe network data editing method and device | |
| CN111708764A (en) | Method and device for controlling database change version | |
| CN110597821B (en) | Method and device for changing database table structure | |
| CN106155838B (en) | A kind of database back-up data restoration methods and device | |
| CN110134646B (en) | Knowledge platform service data storage and integration method and system | |
| CN107315652B (en) | Data backup method and cloud HDFS system | |
| CN111475602A (en) | Multi-version knowledge graph storage method and device, storage medium and electronic equipment | |
| CN111966656A (en) | Method, system, terminal and storage medium for simulating high-load scene of storage file | |
| CN114924914B (en) | Disk partition table information backup and recovery method and system | |
| CN111125067A (en) | Data maintenance method and device | |
| CN112988701A (en) | Database management method, device, system and storage medium | |
| CN116303777A (en) | Real-time synchronous replication method and system between heterogeneous databases | |
| CN105608235B (en) | The data de-duplication method and system of Backup Data block in oracle database | |
| CN115168291A (en) | Hierarchical directory implementation method and device, electronic equipment and storage medium | |
| CN106547756B (en) | Database creation method and device | |
| CN113641651A (en) | Business data management method, system and computer storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |