CN103488695A - Data synchronizing device and data synchronizing method - Google Patents
Data synchronizing device and data synchronizing method Download PDFInfo
- Publication number
- CN103488695A CN103488695A CN201310392662.3A CN201310392662A CN103488695A CN 103488695 A CN103488695 A CN 103488695A CN 201310392662 A CN201310392662 A CN 201310392662A CN 103488695 A CN103488695 A CN 103488695A
- Authority
- CN
- China
- Prior art keywords
- data
- database
- transaction operation
- synchronized
- metadata entity
- 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
Images
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
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Computing Systems (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)
Abstract
The invention provides a data synchronizing device, comprising a business operating configuration module, a business operating handling module and a data processing module; the business operating configuration module is used for selecting business operation from a first database according to a received operation command; the business operating handling module is used for monitoring the business operation and judging whether the data in the business operation need to be synchronized into a second database according to a monitoring result, and if the judging result is yes, acquiring and caching a metadata entity table corresponding to the business operation; the data processing module is used for synchronizing the data in the business operation into the second database according to the cached metadata entity table and the obtained entity table, corresponding to the metadata entity table, of the second database. Correspondingly, the invention also provides a data synchronizing method. By the technical scheme disclosed by the invention, the data in two databases can be furthest kept synchronized.
Description
Technical field
The present invention relates to technical field of data processing, in particular to a kind of data synchronization unit and method of data synchronization.
Background technology
Traditional enterprise database system be online transaction processing system (OLTP) as the data management means, be mainly used in issued transaction, but it always can not be satisfactory to the support of analyzing and processing.Therefore, people attempt the data in the OLTP database are reprocessed gradually, follow-uply occurred that on-line analytical processing (OLAP) has driven data warehouse technology at interior many application tractions, yet how to allow these two kinds of databases better for enterprises service, how OLTP database in production run being imported in olap database to analyze becomes a problem demanding prompt solution.
The processing mode of current most of enterprise is data according to certain cycle (usually every night or per weekend), import the decision support type data from the affairs type database, yet this mode can cause data not prompt enough, particularly for some forms because data are not comprehensive, cause data that error is arranged and incur loss through delay business decision.
Therefore, need a kind of new data synchronization technology, can make to the full extent two kinds of data in database keep synchronous.
Summary of the invention
The present invention just is being based on the problems referred to above, has proposed a kind of new data synchronization technology, can make to the full extent two kinds of data in database keep synchronous.
In view of this, the present invention proposes a kind of data synchronization unit, comprising: the transaction operation configuration module, for the selection instruction according to receiving, from the first database, select transaction operation; The transaction operation processing module, described transaction operation is monitored, and judged whether the data in described transaction operation to be synchronized to the second database according to monitored results, judgment result is that while being, obtain the metadata entity table that described transaction operation is corresponding, the row cache of going forward side by side; Data processing module, according to the described metadata entity table of buffer memory and the entity list of described second database corresponding with described metadata entity table obtained, be synchronized to described the second database by the data in described transaction operation.
Wherein, the first database can be the Transaction Processing database, and the second database can be online analytical processing database, and data processing module is the real-time described metadata entity table that obtains buffer memory.By this technical scheme, can effectively policer operation affairs, timely the data in the Transaction Processing database are synchronized in online analytical processing database, guarantee the efficiently and accurately of decision-making.
In technique scheme, preferably, described data processing module also for, quantity to the described metadata entity table of buffer memory is added up, when described quantity surpasses predetermined number, the data according to described predetermined number gradation in transaction operation that described metadata entity table is corresponding are synchronized to described the second database.
In this technical scheme, if the quantity of the metadata entity table of a buffer memory is too much, if these a plurality of metadata entity tables are synchronized to the second database so simultaneously, may cause lock in time long, the phenomenon got congestion, therefore limit at every turn the synchronously data corresponding to metadata entity table of predetermined number.Such as, predetermined number is 50, and the quantity of the metadata entity table of a buffer memory is 70, system will be synchronized to the data in 70 metadata entity tables in the second database at twice so, i.e. data in synchronous 50 metadata entity tables for the first time, remaining data, after synchronously completing for the first time, then are carried out synchronous.And, because every hyposynchronous time of reality is very short, therefore, in these 70 data of user, be simultaneously synchronous, difference on life period not.
In technique scheme, preferably, described data processing module also for, the quantity of the described metadata entity table of buffer memory is added up, when described quantity does not reach predetermined number, the data by described metadata entity table in corresponding transaction operation are synchronized to described the second database.
In this technical scheme, if the data of the metadata entity table of a buffer memory do not reach predetermined number, so can directly by these metadata entity tables, corresponding data all be synchronized to the second database, thus reach the effect of real time data synchronization.
In technique scheme, preferably, also comprise: mark module, carry out mark to the described data that are synchronized to described the second database.
In this technical scheme, in order to distinguish synchronized data in buffer memory and synchrodata not, can on synchronous data, add mark.
In technique scheme, preferably, also comprise: the cleaning module, regularly the described data of described mark module mark are cleared up.
In this technical scheme, for the promptness that guarantees that data are synchronous, can regularly to the synchronized data in buffer memory, be cleared up.
According to a further aspect in the invention, also provide a kind of method of data synchronization, having comprised: step 202, according to the selection instruction received, from the first database, select transaction operation; Step 204, described transaction operation is monitored, and judged whether the data in described transaction operation to be synchronized to the second database according to monitored results, judgment result is that while being, obtain the metadata entity table that described transaction operation is corresponding, the row cache of going forward side by side; Step 206, the real-time described metadata entity table that obtains buffer memory, according to the described metadata entity table of buffer memory and the entity list of described second database corresponding with described metadata entity table obtained, the data in described transaction operation are synchronized to described the second database.
Wherein, the first database can be the Transaction Processing database, the second database can be online analytical processing database, by this technical scheme, can effectively policer operation affairs, timely the data in the Transaction Processing database are synchronized in online analytical processing database, guarantee the efficiently and accurately of decision-making.
In technique scheme, preferably, step 206 also comprises: the quantity to the described metadata entity table of buffer memory is added up, when described quantity surpasses predetermined number, the data according to described predetermined number gradation in transaction operation that described metadata entity table is corresponding are synchronized to described the second database.
In this technical scheme, if the quantity of the metadata entity table of a buffer memory is too much, if these a plurality of metadata entity tables are synchronized to the second database so simultaneously, may cause lock in time long, the phenomenon got congestion, therefore limit at every turn the synchronously data corresponding to metadata entity table of predetermined number.Such as, predetermined number is 50, and the quantity of the metadata entity table of a buffer memory is 70, system will be synchronized to the data in 70 metadata entity tables in the second database at twice so, i.e. data in synchronous 50 metadata entity tables for the first time, remaining data, after synchronously completing for the first time, then are carried out synchronous.And, because every hyposynchronous time of reality is very short, therefore, in these 70 data of user, be simultaneously synchronous, difference on life period not.
In technique scheme, preferably, described step 206 also comprises, the quantity of the described metadata entity table of buffer memory is added up, when described quantity does not reach predetermined number, the data by described metadata entity table in corresponding transaction operation are synchronized to described the second database.
In this technical scheme, if the data of the metadata entity table of a buffer memory do not reach predetermined number, so can directly by these metadata entity tables, corresponding data all be synchronized to the second database, thus reach the effect of real time data synchronization.
In technique scheme, preferably, described step 206 also comprises: the described data that are synchronized to described the second database are carried out to mark.
In this technical scheme, in order to distinguish synchronized data in buffer memory and synchrodata not, can on synchronous data, add mark.
In technique scheme, preferably, also comprise: step 208, regularly the described data of mark are cleared up.
In this technical scheme, for the promptness that guarantees that data are synchronous, can regularly to the synchronized data in buffer memory, be cleared up.
By above technical scheme, can make to the full extent two kinds of data in database keep synchronous.
The accompanying drawing explanation
Fig. 1 shows the block diagram of data synchronization unit according to an embodiment of the invention;
Fig. 2 shows the process flow diagram of method of data synchronization according to an embodiment of the invention;
Fig. 3 shows the structural drawing of data synchronization unit according to an embodiment of the invention;
Fig. 4 shows the particular flow sheet of method of data synchronization according to an embodiment of the invention.
Embodiment
In order more clearly to understand above-mentioned purpose of the present invention, feature and advantage, below in conjunction with the drawings and specific embodiments, the present invention is further described in detail.It should be noted that, in the situation that do not conflict, the application's embodiment and the feature in embodiment can combine mutually.
A lot of details have been set forth in the following description so that fully understand the present invention; but; the present invention can also adopt other to be different from other modes described here and implement, and therefore, protection scope of the present invention is not subject to the restriction of following public specific embodiment.
Fig. 1 shows the block diagram of data synchronization unit according to an embodiment of the invention.
As shown in Figure 1, data synchronization unit 100 according to an embodiment of the invention, comprising: transaction operation configuration module 102, for the selection instruction according to receiving, from the first database, select transaction operation; Transaction operation processing module 104, described transaction operation is monitored, and judged whether the data in described transaction operation to be synchronized to the second database according to monitored results, judgment result is that while being, obtain the metadata entity table that described transaction operation is corresponding, the row cache of going forward side by side; Data processing module 106, according to the described metadata entity table of buffer memory and the entity list of described second database corresponding with described metadata entity table obtained, be synchronized to described the second database by the data in described transaction operation.
Wherein, the first database can be the Transaction Processing database, the second database can be online analytical processing database, by this technical scheme, can effectively policer operation affairs, timely the data in the Transaction Processing database are synchronized in online analytical processing database, guarantee the efficiently and accurately of decision-making.
In technique scheme, preferably, described data processing module 106 also for, quantity to the described metadata entity table of buffer memory is added up, when described quantity surpasses predetermined number, the data according to described predetermined number gradation in transaction operation that described metadata entity table is corresponding are synchronized to described the second database.
In this technical scheme, if the quantity of the metadata entity table of a buffer memory is too much, if these a plurality of metadata entity tables are synchronized to the second database so simultaneously, may cause lock in time long, the phenomenon got congestion, therefore limit at every turn the synchronously data corresponding to metadata entity table of predetermined number.Such as, predetermined number is 50, and the quantity of the metadata entity table of a buffer memory is 70, system will be synchronized to the data in 70 metadata entity tables in the second database at twice so, i.e. data in synchronous 50 metadata entity tables for the first time, remaining data, after synchronously completing for the first time, then are carried out synchronous.And, because every hyposynchronous time of reality is very short, therefore, in these 70 data of user, be simultaneously synchronous, difference on life period not.
In technique scheme, preferably, described data processing module 106 also for, the quantity of the described metadata entity table of buffer memory is added up, when described quantity does not reach predetermined number, the data by described metadata entity table in corresponding transaction operation are synchronized to described the second database.
In this technical scheme, if the data of the metadata entity table of a buffer memory do not reach predetermined number, so can directly by these metadata entity tables, corresponding data all be synchronized to the second database, thus reach the effect of real time data synchronization.
In technique scheme, preferably, also comprise: mark module 108, carry out mark to the described data that are synchronized to described the second database.
In this technical scheme, in order to distinguish synchronized data in buffer memory and synchrodata not, can on synchronous data, add mark.
In technique scheme, preferably, also comprise: cleaning module 110, regularly the described data of described mark module 108 marks are cleared up.
In this technical scheme, for the promptness that guarantees that data are synchronous, can regularly to the synchronized data in buffer memory, be cleared up.
Fig. 2 shows the process flow diagram of method of data synchronization according to an embodiment of the invention.
As shown in Figure 2, method of data synchronization according to an embodiment of the invention comprises: step 202, according to the selection instruction received, from the first database, select transaction operation; Step 204, described transaction operation is monitored, and judged whether the data in described transaction operation to be synchronized to the second database according to monitored results, judgment result is that while being, obtain the metadata entity table that described transaction operation is corresponding, the row cache of going forward side by side; Step 206, according to the described metadata entity table of buffer memory and the entity list of described second database corresponding with described metadata entity table obtained, be synchronized to described the second database by the data in described transaction operation.
Wherein, the first database can be the Transaction Processing database, the second database can be online analytical processing database, by this technical scheme, can effectively policer operation affairs, timely the data in the Transaction Processing database are synchronized in online analytical processing database, guarantee the efficiently and accurately of decision-making.
In technique scheme, preferably, step 206 also comprises: the quantity to the described metadata entity table of buffer memory is added up, when described quantity surpasses predetermined number, the data according to described predetermined number gradation in transaction operation that described metadata entity table is corresponding are synchronized to described the second database.
In this technical scheme, if the quantity of the metadata entity table of a buffer memory is too much, if these a plurality of metadata entity tables are synchronized to the second database so simultaneously, may cause lock in time long, the phenomenon got congestion, therefore limit at every turn the synchronously data corresponding to metadata entity table of predetermined number.Such as, predetermined number is 50, and the quantity of the metadata entity table of a buffer memory is 70, system will be synchronized to the data in 70 metadata entity tables in the second database at twice so, i.e. data in synchronous 50 metadata entity tables for the first time, remaining data, after synchronously completing for the first time, then are carried out synchronous.And, because every hyposynchronous time of reality is very short, therefore, in these 70 data of user, be simultaneously synchronous, difference on life period not.
In technique scheme, preferably, described step 206 also comprises, the quantity of the described metadata entity table of buffer memory is added up, when described quantity does not reach predetermined number, the data by described metadata entity table in corresponding transaction operation are synchronized to described the second database.
In this technical scheme, if the data of the metadata entity table of a buffer memory do not reach predetermined number, so can directly by these metadata entity tables, corresponding data all be synchronized to the second database, thus reach the effect of real time data synchronization.
In technique scheme, preferably, described step 206 also comprises: the described data that are synchronized to described the second database are carried out to mark.
In this technical scheme, in order to distinguish synchronized data in buffer memory and synchrodata not, can on synchronous data, add mark.
In technique scheme, preferably, also comprise: step 208, regularly the described data of mark are cleared up.
In this technical scheme, for the promptness that guarantees that data are synchronous, can regularly to the synchronized data in buffer memory, be cleared up.
Fig. 3 shows the structural drawing of data synchronization unit according to an embodiment of the invention.
As shown in Figure 3, data synchronization unit 300 comprises according to an embodiment of the invention: transaction operation configuration module 302, transaction operation processing module 304 and data processing module 306, below be described in detail each module.
Transaction operation configuration module 302: be responsible for providing configurable transaction operation module, for the visualization interface designated key, need to carry out the transaction operation that real-time synchronization stores olap database into.
Transaction operation processing module 304: be responsible for the business datum that the regular collection of the business operation the configured processing triggered is resolved in monitoring, comprise set<OLTP metadata entity, transaction operation rule, OLAP metadata entity >.Wherein, transaction operation processing module 304 realizes principle:
At first, according to monitor both transactions, operate, monitor the operation triggered according to the affairs rule configured, data are processed into to the data with certain data structure, the present invention adopts MapList<OLTP metadata entity, the transaction operation rule > record entity and respective operations regular data, adopt Map<OLTP metadata entity .OLAP metadata entity > record disparate databases entity correspondence.
Secondly, when MapList<OLTP metadata entity, the transaction operation rule > middle OLTP metadata entity=current entity, during transaction operation rule=current operation, obtain OLTP metadata entity correspondence database table, the network latency copied to OLAP in order to reduce frequent OLTP, the present invention adopts an interim buffer structure, data in corresponding database table are recorded in a buffer memory, buffer memory adopts the temporary table structure, temporary table structure [OLTP entity table name, entity list data field 1.n, OLAP entity list], and set a threshold value M, but table data number=M in buffer memory, this data cached being synchronized in olap database, and identification data is synchronous.
Regularly empty data in the synchronous buffer memory of sign, and continue the current transaction operation of monitoring.
When needs only carry out when synchronous some field of entity, said apparatus can also expanded configuration metadata entity field mappings.
Data processing module 306: the data assembling to the transaction operation processing module becomes the data object structure, synchronously processes in olap database.
Fig. 4 shows the particular flow sheet of method of data synchronization according to an embodiment of the invention.
As shown in Figure 4, the idiographic flow of method of data synchronization is as follows according to an embodiment of the invention:
Whether step 406, need synchronous OLAP affairs according to the transaction operation rule judgment monitored, and when judgment result is that, is, enters step 408, when the determination result is NO, enters step 404.Wherein, concrete criterion is, judges current whether transaction operation the operation, if operated, needs synchronously, if operated, do not need synchronous.
Below cite an actual example and describe technical scheme of the present invention in detail.
Illustrate: in production environment, need monitoring execution of order situation, for decision analysis.
At first: the needs that configure this production order carry out real-time synchronization to the operation in decision system, and in this example, operation comprises: order goes into operation, order completion operation.Form entity and respective operations regular data set MapList<production order metadata entity, order goes into operation, the order completion >, Map<tmo, amo >.
Secondly: the monitoring current operation, if(current operation entity==production order) & & (current operation==go into operation or order completion of order) time, the processing selecting service data, be stored into buffer memory temporary table database TmpTable[tmo, billcode, num.., amo], and current threshold M=3000 is set, in the time of data in TmpTable table=M, synchronously in this table, be designated in the amo table be not synchronized in olap database.
More than be described with reference to the accompanying drawings technical scheme of the present invention, by technical scheme of the present invention, can have made to the full extent two kinds of data in database keep synchronous.
The foregoing is only the preferred embodiments of the present invention, be not limited to the present invention, for a person skilled in the art, the present invention can have various modifications and variations.Within the spirit and principles in the present invention all, any modification of doing, be equal to replacement, improvement etc., within all should being included in protection scope of the present invention.
Claims (10)
1. a data synchronization unit, is characterized in that, comprising:
The transaction operation configuration module for the selection instruction according to receiving, is selected transaction operation from the first database;
The transaction operation processing module, described transaction operation is monitored, and judged whether the data in described transaction operation to be synchronized to the second database according to monitored results, judgment result is that while being, obtain the metadata entity table that described transaction operation is corresponding, the row cache of going forward side by side;
Data processing module, according to the described metadata entity table of buffer memory and the entity list of described second database corresponding with described metadata entity table obtained, be synchronized to described the second database by the data in described transaction operation.
2. data synchronization unit according to claim 1, it is characterized in that, described data processing module also for, quantity to the described metadata entity table of buffer memory is added up, when described quantity surpasses predetermined number, the data according to described predetermined number gradation in transaction operation that described metadata entity table is corresponding are synchronized to described the second database.
3. data synchronization unit according to claim 1, it is characterized in that, described data processing module also for, quantity to the described metadata entity table of buffer memory is added up, when described quantity does not reach predetermined number, the data by described metadata entity table in corresponding transaction operation are synchronized to described the second database.
4. according to the described data synchronization unit of any one in claims 1 to 3, it is characterized in that, also comprise:
Mark module, carry out mark to the described data that are synchronized to described the second database.
5. data synchronization unit according to claim 4, is characterized in that, also comprises:
The cleaning module, regularly cleared up the described data of described mark module mark.
6. a method of data synchronization, is characterized in that, comprising:
Step 202 according to the selection instruction received, is selected transaction operation from the first database;
Step 204, described transaction operation is monitored, and judged whether the data in described transaction operation to be synchronized to the second database according to monitored results, judgment result is that while being, obtain the metadata entity table that described transaction operation is corresponding, the row cache of going forward side by side;
Step 206, according to the described metadata entity table of buffer memory and the entity list of described second database corresponding with described metadata entity table obtained, be synchronized to described the second database by the data in described transaction operation.
7. method of data synchronization according to claim 6, is characterized in that, step 206 also comprises:
Quantity to the described metadata entity table of buffer memory is added up, and when described quantity surpasses predetermined number, the data according to described predetermined number gradation in transaction operation that described metadata entity table is corresponding are synchronized to described the second database.
8. method of data synchronization according to claim 6, is characterized in that, described step 206 also comprises,
Quantity to the described metadata entity table of buffer memory is added up, and when described quantity does not reach predetermined number, the data by described metadata entity table in corresponding transaction operation are synchronized to described the second database.
9. according to the described method of data synchronization of any one in claim 6 to 8, it is characterized in that, described step 206 also comprises:
The described data that are synchronized to described the second database are carried out to mark.
10. method of data synchronization according to claim 9, is characterized in that, also comprises:
Step 208, regularly cleared up the described data of mark.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310392662.3A CN103488695A (en) | 2013-09-02 | 2013-09-02 | Data synchronizing device and data synchronizing method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310392662.3A CN103488695A (en) | 2013-09-02 | 2013-09-02 | Data synchronizing device and data synchronizing method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN103488695A true CN103488695A (en) | 2014-01-01 |
Family
ID=49828921
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201310392662.3A Pending CN103488695A (en) | 2013-09-02 | 2013-09-02 | Data synchronizing device and data synchronizing method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103488695A (en) |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105653652A (en) * | 2015-12-28 | 2016-06-08 | 上海瀚银信息技术有限公司 | Data synchronization method and system |
| CN108427689A (en) * | 2017-02-15 | 2018-08-21 | 北京国双科技有限公司 | Information acquisition method and device |
| CN109947801A (en) * | 2019-02-25 | 2019-06-28 | 交通银行股份有限公司 | Database in phase system, method and device |
| CN110019873A (en) * | 2017-12-25 | 2019-07-16 | 深圳市优必选科技有限公司 | Human face data processing method, device and equipment |
| CN110019191A (en) * | 2017-09-21 | 2019-07-16 | 阿里巴巴集团控股有限公司 | Database information processing method and processing device |
| CN110990435A (en) * | 2019-12-03 | 2020-04-10 | 秒针信息技术有限公司 | Data synchronization method, device and computer readable storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101047549A (en) * | 2006-04-10 | 2007-10-03 | 华为技术有限公司 | Data synchronous system and its method |
| EP1610235B1 (en) * | 2004-06-23 | 2009-11-25 | Sap Ag | A data processing system and method |
| CN101706795A (en) * | 2009-11-30 | 2010-05-12 | 上海世范软件技术有限公司 | Method for synchronizing data of database in active/standby server |
-
2013
- 2013-09-02 CN CN201310392662.3A patent/CN103488695A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1610235B1 (en) * | 2004-06-23 | 2009-11-25 | Sap Ag | A data processing system and method |
| CN101047549A (en) * | 2006-04-10 | 2007-10-03 | 华为技术有限公司 | Data synchronous system and its method |
| CN101706795A (en) * | 2009-11-30 | 2010-05-12 | 上海世范软件技术有限公司 | Method for synchronizing data of database in active/standby server |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105653652A (en) * | 2015-12-28 | 2016-06-08 | 上海瀚银信息技术有限公司 | Data synchronization method and system |
| CN108427689A (en) * | 2017-02-15 | 2018-08-21 | 北京国双科技有限公司 | Information acquisition method and device |
| CN110019191A (en) * | 2017-09-21 | 2019-07-16 | 阿里巴巴集团控股有限公司 | Database information processing method and processing device |
| CN110019873A (en) * | 2017-12-25 | 2019-07-16 | 深圳市优必选科技有限公司 | Human face data processing method, device and equipment |
| CN109947801A (en) * | 2019-02-25 | 2019-06-28 | 交通银行股份有限公司 | Database in phase system, method and device |
| CN110990435A (en) * | 2019-12-03 | 2020-04-10 | 秒针信息技术有限公司 | Data synchronization method, device and computer readable storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103488695A (en) | Data synchronizing device and data synchronizing method | |
| CN110292775B (en) | Method and device for acquiring difference data | |
| CN101102281B (en) | Data processing method for reporting a large number of data in mobile communication system | |
| CN104301360B (en) | A kind of method of logdata record, log server and system | |
| CN104182898B (en) | The method that banking system carries out amended record to the on-line transaction occurred during night mode | |
| CN102340415B (en) | Server cluster system and monitoring method thereof | |
| CN104423960B (en) | A kind of method and system of project continuous integrating | |
| CN104966172A (en) | Large data visualization analysis and processing system for enterprise operation data analysis | |
| CN110362632A (en) | A kind of method of data synchronization, device, equipment and computer readable storage medium | |
| CN106557592A (en) | Method of data synchronization, device and server cluster | |
| CN106557497A (en) | A kind of method of data synchronization and device | |
| CN109254901B (en) | A kind of Monitoring Indexes method and system | |
| CN102736725A (en) | Energy-saving hard disk control method and device and central processing unit | |
| CN109460393B (en) | Big data-based visual system for pre-inspection and pre-repair | |
| CN109634970A (en) | Table method of data synchronization, equipment, storage medium and device | |
| CN102779138A (en) | Hard disk access method of real time data | |
| CN104317957A (en) | Open platform and system for processing reports and report processing method | |
| CN111221890B (en) | Automatic monitoring and early warning method and device for universal index class | |
| CN111400376B (en) | Method and device for building population analysis platform based on telecommunication data | |
| CN102801548A (en) | Intelligent early warning method, device and information system | |
| CN104991741B (en) | A kind of situation adaptation power network big data storage method based on key-value model | |
| CN102129619A (en) | Service data processing method and system based on cloud storage | |
| CN104281932A (en) | Intelligent shift acquisition device and method | |
| CN109982250A (en) | A kind of position data acquisition method, equipment and computer storage medium | |
| Zhou et al. | An ETL strategy for real-time data warehouse |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information |
Address after: 100094 Haidian District North Road, Beijing, No. 68 Applicant after: Yonyou Network Technology Co., Ltd. Address before: 100094 Beijing city Haidian District North Road No. 68, UFIDA Software Park Applicant before: UFIDA Software Co., Ltd. |
|
| COR | Change of bibliographic data | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20140101 |