CN107346314A - A kind of database unidirectional synchronization method - Google Patents
A kind of database unidirectional synchronization method Download PDFInfo
- Publication number
- CN107346314A CN107346314A CN201610295087.9A CN201610295087A CN107346314A CN 107346314 A CN107346314 A CN 107346314A CN 201610295087 A CN201610295087 A CN 201610295087A CN 107346314 A CN107346314 A CN 107346314A
- Authority
- CN
- China
- Prior art keywords
- database
- record
- source
- data
- synchronized
- 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.)
- Pending
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/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
- G06F16/275—Synchronous replication
Abstract
The present invention relates to the database unidirectional synchronization method between a kind of database.This method comprises the steps：Inquire the data to be synchronized in source database；Check that to be synchronized be recorded in target database whether there is, operation or insertion operation are updated or without simultaneously operating according to inspection result；Inquire the available data in target database；And check that the data in target database whether there is in source database, delete the record either distance pole record or without simultaneously operating according to inspection result.It according to the database unidirectional synchronization method between the database of the present invention, can be decoupled with business, and need to be only that the one-way data that can be achieved between distinct type data-base, different structure table data is synchronous by easy configuration.
Description
Technical field
The present invention relates to the method for data synchronization of database, more particularly to the isomeric relationship type database unidirectional synchronization method of configurableization based on Spring JDBC.
Background technology
On database synchronization, there is its special product in each large database concept manufacturer.Such as Oracle Data
Guard、Golden Gate.But they are mainly used in the consistent situation of database table structure data.The data syn-chronization between different list structured data storehouses can not be realized.Common code is realized and often linked up with service logic, does not possess versatility and flexibility.
In enterprise applies, the situation that a basic data is used by different system is frequently present of.If each system is required for safeguarding these basic datas, then the workload of maintenance will become very heavy, and the uniformity of data is difficult to be protected.In order to mitigate maintenance workload and ensure data consistency, generally require to be defined by some storehouse data, other databases are as shared the basic data, then by partial data synchronization in the past.
The content of the invention
In view of the above problems, the present invention proposes that a kind of needs progress easy configuration to can be realized as the database unidirectional synchronization method between distinct type data-base, different structure table database.
Database unidirectional synchronization method between the database of the present invention, it is characterised in that this method comprises the steps：
Source database query steps：Inquire the data to be synchronized in source database；
First record comparison step：Check that to be synchronized be recorded in target database whether there is, operation or insertion operation are updated or without simultaneously operating according to inspection result；
Target database query steps：Inquire the available data in target database；And
Second record comparison step：Check that the data in target database whether there is in source database, the record either distance pole record or without simultaneously operating delete according to inspection result.
Preferably, every a line record in source database and target database is mapped to a Map object.
Preferably, the Key using the database table field of source database and target database as the Map objects, the Value using the value of literary name section in the row as corresponding K ey.
Preferably, in the source database query steps, the data to be synchronized in source database are inquired according to " source storehouse table table name to be synchronized ", " source table field to be synchronized ", wherein, " source storehouse table table name to be synchronized ", " source table field to be synchronized " they are configurable parameter.
Preferably, following sub-steps are included in the described first record comparison step：
Source database data record to be synchronized is traveled through, " object table records unique mark field " is inquired about in target database according to the value of " source token record unique mark field " has the record of identical value；
If the record in target database be present, whether the value for comparing " object table field to be synchronized " is consistent with the value of " source table field to be synchronized "；
If there is the record and consistent with the record in source database in target database, simultaneously operating need not then be performed, if there is the record but not quite identical, the renewal that target database is then carried out according to source database operates, if there is no the record, then the record renewal in source database is arrived target database by the method for synchronization according to the rules.
Preferably, the regulation method of synchronization includes one of following manner：
Storage renewal, incremental update, strong synchronous, weak synchronization.
Preferably, the second record comparison step includes following sub-steps：
The object table data inquired about in target database；
The source table data inquired about in source database；
Compare difference between the two, wherein, if the record in the table of source be present, without any operation, delete the data in object table if the record is not present in the table of source or the record is labeled.
Preferably, in the sub-step of the object table data in inquiring about target database, the data record in target database is inquired according to " target table name ", " object table records unique mark field ".
Preferably, in the sub-step of the source table data in inquiring about source database, each data record of object table is traveled through, according to the value of " object table records unique mark field " of record, " source token record unique mark field " is inquired about in the table of source has the record of identical value.
Preferably, in the sub-step for comparing difference between the two, if the record in the table of source be present, then without any operation, if in the case of the record is not present in the table of source, if the regulation method of synchronization is strong synchronous, delete the record, if the regulation method of synchronization is weak synchronization, " object table tag field " state for updating the record in object table is deletion state.
As described above, in the present invention, by the way that every a line record of database is mapped into a Map object, literary name section is using as the Key of the Map objects, Value of the value as corresponding K ey corresponding to literary name section in row record, the multirow record of database are mapped as the set of a Map object.So, either what kind of table data can be stored with same data structure, thereby, it is possible to by simultaneously operating and table structure decoupling, that is, can be decoupled with specific business.And, configurable item is arranged to by the way that object library Database Connection Parameters, source library database Connecting quantity, target database table table name to be synchronized, source database table table name to be synchronized, object table field to be synchronized, source table field to be synchronized, object table and source table field mapping relations to be synchronized, object table are recorded into unique mark field, source token record unique mark section, data syn-chronization mode and target database tag field, the one-way data that can be realized as by easy configuration between distinct type data-base, different structure table data is synchronous.
Brief description of the drawings
Fig. 1 illustrates the schematic diagram for being used to realize the MAP of the mapping of data-base recording in the present invention.
Fig. 2 is the flow chart of the database unidirectional synchronization method between the database for representing the present invention.
Fig. 3 is the schematic diagram of the database unidirectional synchronization method between the database for representing one embodiment of the invention.
Embodiment
What is be described below is some in multiple embodiments of the invention, it is desirable to provide to the basic understanding of the present invention.It is not intended as the crucial or conclusive key element for confirming the present invention or limits scope of the claimed.
First, in the present invention, using JDBC technologies as database access technology.JDBC can support frequently-used data storehouse type, shield underlying database difference, there is provided unified database access interface.Specifically, JDBC is that a kind of JavaAPI for being used to perform SQL statement can provide unified access for a variety of relational databases, and the class and interface that it is write by one group with Java language form.JDBC provides a kind of benchmark, can build the instrument and interface of higher level accordingly, database development personnel is write database application.Wherein, JDBC JavaDataBaseConnectivity, java database connect；SQL is StructuredQueryLanguage SQLs；API is ApplicationProgrammingInterface, application programming interface.The relevant introduction of JDBC technologies referring also to：
http://www.oracle.com/technetwork/java/javase/jdbc/index.html。
In addition, hereinafter also the relevant introduction for the Spring JDBC technologies mentioned may refer to:
http://docs.spring.io/spring/docs/current/spring-framework-reference/html/jdbc.html。
In the present invention, the database of data syn-chronization to be implemented is considered as target database, the database of offer data source is considered as source database, and the connection to two databases is established with JDBC technologies.
Secondly, realization must synchronously inquire target database and the data record of source database, compare the difference between record and handled accordingly.If accessing framework using OODB Object Oriented Data Base, because token record will be mapped as corresponding object, then synchronous realization is coupled with specific business, can not meet the principle of versatility.If using primary JDBC, table data are mothballed in ResultSet, although ResultSet is also a kind of general data object, it operates cumbersome.But another general data object is employed in the present invention：Map, for realizing the mapping with data-base recording.
Fig. 1 illustrates the schematic diagram for being used to realize the MAP of the mapping of data-base recording in the present invention.
As shown in figure 1, every a line record of database is mapped to a Map object, literary name section is using as the Key of the Map objects, and value is used as corresponding K ey corresponding to literary name section during the row records（That is key）Value（It is worth）.And the multirow record of database is mapped as the set of a Map object.So, either what kind of table data can use same data structure（Map or Map set）To store, so that by simultaneously operating and table structure decoupling, that is, can be decoupled with specific business.
Spring
JDBC is the encapsulation based on JDBC technologies, in that context it may be convenient to database query result is encapsulated as to the set of Map objects and Map objects, therefore employs Spring JDBC in the present invention to simplify to database manipulation.It mainly assists to complete three work：1. read source database table data；2. read target database table data；3. update target database.
Finally, it is that synchronizing process is abstracted.Common to be achieved in that, simultaneously operating is generally cured in code.In order to realize versatility, the logic synchronously realized is devised in the present invention（That is the flow of synchronous method）And the key point in synchronizing process is extracted, extracted and be used as configurable parameter, it is achieved thereby that configurableization of simultaneously operating.
Fig. 2 is the flow chart of the database unidirectional synchronization method between the database for representing the present invention.
As shown in Fig. 2 the database unidirectional synchronization method between the database of the present invention comprises the steps：
Step S100：Source database query steps, for inquiring the data to be synchronized in source database；
Step S200：First record comparison step, for checking that to be synchronized be recorded in target database whether there is, such as exist and completely the same, be then not required to be operated；As exist but it is not quite identical, then according to source database carry out target database renewal operation；If there is no then performing insertion operation（Synchronous recording is inserted into target database）；
Step S300：Target database query steps, for inquiring the available data in target database；And
Step S400：First record comparison step, for checking that the data in target database whether there is in source database, is not required to operate if existing, data in delete target database if being not present, or the record is labeled.
In the present invention, configurable key parameter has following parameters：
（1）Object library Database Connection Parameters：
For positioning target database.
（2）Source library database Connecting quantity：
For positioning source database.
（3）Target database table table name to be synchronized：
For positioning the object table of target database.
（4）Source database table table name to be synchronized：
For positioning the source table in source database.
（5）Object table field to be synchronized:
For positioning the literary name section for needing to update in object table.
（6）Source table field to be synchronized:
For literary name section where data to be synchronized in query source table.
（7）Object table, source table field mapping relations to be synchronized:
For determining how the respective field in the value renewal of each field in the table of source or insertion object table.
（8）Object table records unique mark field and source token record unique mark section:
Source token record unique mark section whether there is, and judge that object table is recorded in the table of source and whether there is together with object table record unique mark field for judging that source table is recorded in object table.
（9）Data syn-chronization mode:
Data syn-chronization mode main definitions have storage renewal, incremental update, strong synchronous, weak four kinds of modes of synchronization:
Storage renewal refers to only performs renewal to existing record in object table, for the synchronous mode of acquiescence；
Incremental update refers to be updated for having recorded to do in object table, and the record for having for source table and not having in object table performs insertion operation；
Strong synchronously refer to is updated for having recorded to do in object table, and the record for having for source table and not having in object table performs insertion operation, and deletion action is performed for the record for not having and having in object table in the table of source；
Weak synchronously refer to updates for having recorded to do in object table, and the record for having for source table and not having in object table performs insertion operation, is operated for the record execution flag for not having and having in object table in the table of source.
（10）Target database tag field：
Nonessential parameter, only used under " weak synchronization " pattern.
In the present invention, the attribute of database connection（That is object library Database Connection Parameters and source library database Connecting quantity）Configurable item is arranged to, therefore, the data syn-chronization of heterogeneous database can be supported in the present invention.And, target database table name to be synchronized, field to be synchronized and source table table name to be synchronized, field to be synchronized are disposed as configurable parameter, the different pieces of information table that database can be directed to when carrying out data syn-chronization in the present invention for being then is carried out, moreover, synchronous literary name section also need not be identical.
Below, illustrated for the database unidirectional synchronization method between the database of one embodiment of the invention.
Fig. 3 is the schematic diagram of the database unidirectional synchronization method between the database for representing one embodiment of the invention.
As shown in figure 3, step 1:Inquire about the data to be synchronized of source database.
Specifically, the data record to be synchronized in source database is inquired according to " target database table table name to be synchronized ", " source table field to be synchronized ".Such as looked into newly to source table 1, source table 2 according to " target database table table name to be synchronized " in figure 3.
Step 2：Target database is inquired about, whether there is with checking that data to be synchronized are recorded in target database.
Specifically, as shown in figure 3, inquiring object table 1, object table 2 according to " target database table table name to be synchronized ".Data record to be synchronized in ergodic source table 1,2 one by one, according to the value of " source marks record unique mark field " of record, " record of " object table record unique mark field " with identical value is being inquired about in object table 1, object table 2 ".
Step 3：Comparison sheet records difference.
If object table has the record, whether comparison object table is consistent with the value of " source table field to be synchronized " with the value of " the object table field to be synchronized " of the record of source table.
Step 4：Update object table data.
If object table has the record, and consistent with source token record, then simultaneously operating need not be performed；
If object table has the record, but inconsistent with source token record, then the data renewal that source is marked to record according to " object table, source table field mapping relations to be synchronized " records to object table；
If the record is not present in object table, according to " method of synchronization " value, data insertion operation is performed under " incremental update ", " strong synchronous ", " weak synchronization " pattern.
Then, in the present embodiment, according to " method of synchronization " value, continue subsequent operation under " strong synchronous ", " weak synchronization " pattern, comprise the following steps that shown in（Wherein, step 5~step 8 does not represent in the accompanying drawings）：
Step 5：Inquire about object table data.
Specifically, the data record in target database is inquired according to " target table name ", " object table record unique mark field ".
Step 6：Query source table data.
Specifically, each data record of object table is traveled through one by one, and according to the value of record " object table records unique mark field ", " source token record unique mark field " is inquired about in " source table " has the record of identical value.
Step 7：Comparison sheet records difference.
Step 8：Update object table data.
Specifically, if the record in the table of source be present, without any operation；If there is no the record, then according to " method of synchronization " value, the record is deleted under " strong synchronous " pattern；" object table tag field " state that the record in object table is updated under " weak synchronization " pattern is deletion state.
In the present invention, as described above, one side, by the way that every a line record of database is mapped into a Map object, literary name section is using as the Key of the Map objects, Value of the value as corresponding K ey corresponding to literary name section in row record, the multirow record of database are mapped as the set of a Map object.So, either what kind of table data can use same data structure（Map or Map set）To store, thereby, it is possible to by simultaneously operating and table structure decoupling, that is, can be decoupled with specific business.
Second aspect, configurable item is arranged to by the way that object library Database Connection Parameters, source library database Connecting quantity, target database table table name to be synchronized, source database table table name to be synchronized, object table field to be synchronized, source table field to be synchronized, object table and source table field mapping relations to be synchronized, object table are recorded into unique mark field, source token record unique mark section, data syn-chronization mode and target database tag field, the one-way data that can be realized as by easy configuration between distinct type data-base, different structure table data is synchronous.
Example above primarily illustrates the database unidirectional synchronization method between the database of the present invention.Although only the embodiments of some of present invention are described, those of ordinary skill in the art are it is to be appreciated that the present invention can be without departing from its spirit with being implemented in the form of many other in scope.Therefore, the example shown is considered as illustrative and not restrictive with embodiment, and in the case where not departing from the spirit and scope of the present invention as defined in appended claims, the present invention may cover various modification and replacement.
Claims (10)
1. the database unidirectional synchronization method between a kind of database, it is characterised in that this method comprises the steps：
Source database query steps：Inquire the data to be synchronized in source database；
First record comparison step：Check that to be synchronized be recorded in target database whether there is, operation or insertion operation are updated or without simultaneously operating according to inspection result；
Target database query steps：Inquire the available data in target database；And
Second record comparison step：Check that the data in target database whether there is in source database, the record either distance pole record or without simultaneously operating delete according to inspection result.
2. the database unidirectional synchronization method between database as claimed in claim 1, it is characterised in that
Every a line record in source database and target database is mapped to a Map object.
3. the database unidirectional synchronization method between database as claimed in claim 2, it is characterised in that
Key using the database table field of source database and target database as the Map objects, the Value using the value of literary name section in the row as corresponding K ey.
4. the database unidirectional synchronization method between database as claimed in claim 2, it is characterised in that
In the source database query steps, the data to be synchronized in source database are inquired according to " source storehouse table table name to be synchronized ", " source table field to be synchronized ", wherein, " source storehouse table table name to be synchronized ", " source table field to be synchronized " they are configurable parameter.
5. the database unidirectional synchronization method between database as claimed in claim 3, it is characterised in that
Include following sub-steps in the described first record comparison step：
Source database data record to be synchronized is traveled through, " object table records unique mark field " is inquired about in target database according to the value of " source token record unique mark field " has the record of identical value；
If the record in target database be present, whether the value for comparing " object table field to be synchronized " is consistent with the value of " source table field to be synchronized "；
If there is the record and consistent with the record in source database in target database, simultaneously operating need not then be performed, if there is the record but not quite identical, the renewal that target database is then carried out according to source database operates, if there is no the record, then the record renewal in source database is arrived target database by the method for synchronization according to the rules.
6. the database unidirectional synchronization method between described database as claimed in claim 5, it is characterised in that
The regulation method of synchronization includes one of following manner：
Storage renewal, incremental update, strong synchronous, weak synchronization.
7. the database unidirectional synchronization method between database as claimed in claim 6, it is characterised in that
Include following sub-steps in the described second record comparison step：
The object table data inquired about in target database；
The source table data inquired about in source database；
Compare difference between the two, wherein, if the record in the table of source be present, without any operation, delete the data in object table if the record is not present in the table of source or the record is labeled.
8. the database unidirectional synchronization method between database as claimed in claim 7, it is characterised in that
In the sub-step of the object table data in inquiring about target database, the data record in target database is inquired according to " target table name ", " object table records unique mark field ".
9. the database unidirectional synchronization method between database as claimed in claim 7, it is characterised in that
In the sub-step of the source table data in inquiring about source database, each data record of object table is traveled through, according to the value of " object table records unique mark field " of record, " source token record unique mark field " is inquired about in the table of source has the record of identical value.
10. the database unidirectional synchronization method between database as claimed in claim 7, it is characterised in that
In the sub-step for comparing difference between the two, if the record in the table of source be present, then without any operation, if in the case of the record is not present in the table of source, if the regulation method of synchronization is strong synchronous, the record is then deleted, if the regulation method of synchronization is weak synchronization, " object table tag field " state for updating the record in object table is deletion state.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610295087.9A CN107346314A (en) | 2016-05-06 | 2016-05-06 | A kind of database unidirectional synchronization method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610295087.9A CN107346314A (en) | 2016-05-06 | 2016-05-06 | A kind of database unidirectional synchronization method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN107346314A true CN107346314A (en) | 2017-11-14 |
Family
ID=60254187
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610295087.9A Pending CN107346314A (en) | 2016-05-06 | 2016-05-06 | A kind of database unidirectional synchronization method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107346314A (en) |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108763256A (en) * | 2018-03-30 | 2018-11-06 | 云南电网有限责任公司信息中心 | A kind of electric power GIS Temporal Model construction method based on Dike-pond modes |
| CN109241183A (en) * | 2018-08-16 | 2019-01-18 | 武汉元鼎创天信息科技有限公司 | A kind of method of data synchronization and system based on socket communication |
| CN110309161A (en) * | 2019-06-06 | 2019-10-08 | 新华三大数据技术有限公司 | A kind of method of data synchronization, device and server |
| CN110750585A (en) * | 2019-10-12 | 2020-02-04 | 南京我爱我家信息科技有限公司 | Improvement of data extraction method |
| CN110909071A (en) * | 2018-09-17 | 2020-03-24 | 北京国双科技有限公司 | Data synchronization method, device and system |
| CN111090648A (en) * | 2019-12-07 | 2020-05-01 | 杭州安恒信息技术股份有限公司 | Relational database data synchronization conflict resolution method |
| CN111400407A (en) * | 2020-04-10 | 2020-07-10 | 浙江大华技术股份有限公司 | Data synchronization method and device, storage medium and electronic device |
| CN111427787A (en) * | 2020-03-26 | 2020-07-17 | 杭州趣维科技有限公司 | Heterogeneous database business data synchronization test method |
| WO2020228184A1 (en) * | 2019-05-13 | 2020-11-19 | 平安科技（深圳）有限公司 | Method and device for comparing table structures in database, computer apparatus, and storage medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070255763A1 (en) * | 2006-04-27 | 2007-11-01 | International Business Machines Corporation | Database replication method and system |
| CN101483651A (en) * | 2009-01-09 | 2009-07-15 | 南京联创科技股份有限公司 | Data transmission method based map queue |
| CN102693324A (en) * | 2012-01-09 | 2012-09-26 | 西安电子科技大学 | Distributed database synchronization system, synchronization method and node management method |
| CN104111937A (en) * | 2013-04-18 | 2014-10-22 | 中兴通讯股份有限公司 | Master database standby database and data consistency testing and repairing method and device of master database and standby database |
| CN104572672A (en) * | 2013-10-15 | 2015-04-29 | 北大方正集团有限公司 | Heterogeneous database synchronization method and application system |
| CN104778225A (en) * | 2015-03-27 | 2015-07-15 | 浙江大学 | Method for synchronizing data in unstructured data multi-storage system |
-
2016
- 2016-05-06 CN CN201610295087.9A patent/CN107346314A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070255763A1 (en) * | 2006-04-27 | 2007-11-01 | International Business Machines Corporation | Database replication method and system |
| CN101483651A (en) * | 2009-01-09 | 2009-07-15 | 南京联创科技股份有限公司 | Data transmission method based map queue |
| CN102693324A (en) * | 2012-01-09 | 2012-09-26 | 西安电子科技大学 | Distributed database synchronization system, synchronization method and node management method |
| CN104111937A (en) * | 2013-04-18 | 2014-10-22 | 中兴通讯股份有限公司 | Master database standby database and data consistency testing and repairing method and device of master database and standby database |
| CN104572672A (en) * | 2013-10-15 | 2015-04-29 | 北大方正集团有限公司 | Heterogeneous database synchronization method and application system |
| CN104778225A (en) * | 2015-03-27 | 2015-07-15 | 浙江大学 | Method for synchronizing data in unstructured data multi-storage system |
Cited By (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108763256A (en) * | 2018-03-30 | 2018-11-06 | 云南电网有限责任公司信息中心 | A kind of electric power GIS Temporal Model construction method based on Dike-pond modes |
| CN109241183A (en) * | 2018-08-16 | 2019-01-18 | 武汉元鼎创天信息科技有限公司 | A kind of method of data synchronization and system based on socket communication |
| CN109241183B (en) * | 2018-08-16 | 2020-12-29 | 武汉元鼎创天信息科技有限公司 | Data synchronization method and system based on socket communication |
| CN110909071A (en) * | 2018-09-17 | 2020-03-24 | 北京国双科技有限公司 | Data synchronization method, device and system |
| WO2020228184A1 (en) * | 2019-05-13 | 2020-11-19 | 平安科技（深圳）有限公司 | Method and device for comparing table structures in database, computer apparatus, and storage medium |
| CN110309161A (en) * | 2019-06-06 | 2019-10-08 | 新华三大数据技术有限公司 | A kind of method of data synchronization, device and server |
| CN110309161B (en) * | 2019-06-06 | 2021-10-29 | 新华三大数据技术有限公司 | Data synchronization method and device and server |
| CN110750585A (en) * | 2019-10-12 | 2020-02-04 | 南京我爱我家信息科技有限公司 | Improvement of data extraction method |
| CN111090648A (en) * | 2019-12-07 | 2020-05-01 | 杭州安恒信息技术股份有限公司 | Relational database data synchronization conflict resolution method |
| CN111090648B (en) * | 2019-12-07 | 2023-05-16 | 杭州安恒信息技术股份有限公司 | Relational database data synchronization conflict resolution method |
| CN111427787A (en) * | 2020-03-26 | 2020-07-17 | 杭州趣维科技有限公司 | Heterogeneous database business data synchronization test method |
| CN111427787B (en) * | 2020-03-26 | 2023-05-30 | 杭州小影创新科技股份有限公司 | Synchronous testing method for service data of heterogeneous database |
| CN111400407A (en) * | 2020-04-10 | 2020-07-10 | 浙江大华技术股份有限公司 | Data synchronization method and device, storage medium and electronic device |
| CN111400407B (en) * | 2020-04-10 | 2023-09-26 | 浙江大华技术股份有限公司 | Data synchronization method and device, storage medium and electronic device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107346314A (en) | A kind of database unidirectional synchronization method | |
| US8954479B2 (en) | End-to-end interoperability and workflows from building architecture design to one or more simulations | |
| US7730097B2 (en) | Smart database | |
| US9659051B2 (en) | Enforcing referential integrity for object data documents | |
| US8024305B2 (en) | Updating a data warehouse schema based on changes in an observation model | |
| US8479158B2 (en) | Business information warehouse toolkit and language for warehousing simplification and automation | |
| US7096231B2 (en) | Export engine which builds relational database directly from object model | |
| CN103544323B (en) | A kind of data-updating method and device | |
| TWI412945B (en) | Retrieving and persisting objects from/to relational databases | |
| US20150046524A1 (en) | Data Management for Mobile Data System | |
| CN101989301B (en) | Index maintenance method for supporting multiple data sources | |
| US20160259831A1 (en) | Methodology supported business intelligence (BI) software and system | |
| CN105144162B (en) | Integrated data base frame | |
| US8805777B2 (en) | Data record collapse and split functionality | |
| US7509627B1 (en) | Method for management of dynamically alterable lifecycles in structured classification domains | |
| US20170097970A1 (en) | Task-execution in a dbms using stored procedures | |
| US20030177117A1 (en) | Metadata system for managing data mining environments | |
| CN104298769A (en) | System and method for synchronizing discrepant data of common domain between databases | |
| AU2014101659A4 (en) | Metadata automated system | |
| CN102760164B (en) | A kind of method of exchanges data between relational database management system and XML data base management system | |
| CN105354671A (en) | Universal configuration management system and enterprise-level information system comprising same | |
| WO2014193470A1 (en) | Method of managing relational data in a single matrix representation | |
| Stumptner et al. | BIAccelerator–a template-based approach for rapid ETL development | |
| JP2003208346A (en) | Reflection system of data base update information and program therefor | |
| JP5542857B2 (en) | Query issuing device, query issuing program, query issuing method |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20171114 |
|
| RJ01 | Rejection of invention patent application after publication |