CN102402600A - Asynchronous collecting method for maintaining consistency of database replicas - Google Patents
Asynchronous collecting method for maintaining consistency of database replicas Download PDFInfo
- Publication number
- CN102402600A CN102402600A CN2011103671057A CN201110367105A CN102402600A CN 102402600 A CN102402600 A CN 102402600A CN 2011103671057 A CN2011103671057 A CN 2011103671057A CN 201110367105 A CN201110367105 A CN 201110367105A CN 102402600 A CN102402600 A CN 102402600A
- Authority
- CN
- China
- Prior art keywords
- data
- duplicate
- local
- complete
- tuple
- 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
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses an asynchronous collecting method for maintaining consistency of database replicas, comprising the steps of: 1) dividing a database differential replica into a complete replica type and a partial replica type; dividing the data into splinters according to the application requirement and storing them into two types of data replicas; 2) comparing the database contents to find the differential data in the complete replica and the partial replica, before modifying the local data, renewing the data and synchronizing the data from the complete replica to the partial replica; 3) after modifying the local data, executing a committing operation, and synchronizing the data from the partial replica to the complete replica. The asynchronous collecting method provided by the invention supports multi-database concurrent changes, overcomes the dependence on the dump file and greatly reduces the dependence on the network stability compared with the online synchronous method realized via an application software.
Description
Technical field
The present invention relates to a kind ofly based on collecting thought, the asynchronous method of data consistency between maintenance data base otherness duplicate belongs to electric power system data library management technical field.
Background technology
In the large-scale monitoring system of Fen Saning, model data is distributed in disparate databases more geographically.Common Distribution Strategy has: centralized: data centralization is deposited; Partition type: data disperse to deposit, but can not repeat between data; Redundance type: each node is all deposited complete data duplicate; Hybrid: above-mentioned three kinds mixing, this is the most complicated, flexible way, i.e. the database otherness duplicate that the present invention is suitable for.
Can be divided into two types for this type otherness duplicate consistency maintaining method: offline synchronization and online synchronous.
Simple offline synchronization method normally exports to dump file with all objects of source database, again dump file is imported the consistance of target database with maintenance and source database.This method for synchronous is extended to indifference opposite sex duplicate with the otherness duplicate according to its extension, and is simple and reliable, but is not suitable for the application of the concurrent modification of a plurality of databases.
Improved offline synchronization method is divided into sliver on demand with all tuples in the source database; The tuple place sliver that needs maintaining coherency in the source database is exported to dump file, again dump file is imported to the original corresponding sliver of covering in the target database.This method has remedied the defective that simple offline synchronization is not supported the concurrent modification of multiple database, but conforming maintenance need increase maintenance difficulties by means of copy, transmission and the merging of a plurality of files of operating system aspect between the storehouse.If can not effectively manage to file, very easily cause the version error of file, increase the inconsistent risk of data.
Online is that application software is after local data base is carried out the write operation success, again through other databases of network mode direct modification synchronously; Or send the message packet that comprises synchronizing information to other database servers.The online problem that has well solved the existence of offline synchronization method synchronously, data consistency is safeguarded and is realized through application software system, can satisfy the demand of using data so flexibly.It is comparatively harsh that but online method for synchronous requires network environment; In case the concurrent modification of multiple database has taken place when network congestion, be easy to cause data inconsistent, even network recovery afterwards; Also possibly can't return to consistent state, thereby cause nonvolatil error in data.Then carrying out data modification in the inconsistent database, involve key word in the table, index, and trigger many constraint condition such as relation between table, also possibly cause the inconsistent expanded range of data.This catastrophic consequence is that system developer and engineering construction person least hope to see.
Summary of the invention
Technical matters to be solved by this invention is that the consistance of realization service data tuple between the otherness duplicate handled the problem of the concurrent modification of multiple database well, and alleviated the degree of dependence of maintenance work to network quality.
For solving the problems of the technologies described above, the present invention provides a kind of maintenance data base duplicate the conforming asynchronous method that collects, and it is characterized in that, may further comprise the steps:
1) database otherness duplicate is divided into two types of complete duplicate and local copy, according to the requirement of using data is divided into sliver and leaves in two types of data duplicates;
2) relatively find out the variance data in complete duplicate and the local copy through data-base content, before revising local data, carry out and upgrade operation, from complete duplicate to the local copy synchrodata;
3) accomplish back execution submit operation revising local data, from local copy to complete duplicate synchrodata.
Said complete duplicate comprises the overall situation, and all are centralized, the partition type data of redundance type data and this node; Local copy comprises the partition type data of redundance type data and this node;
Said submit operation is meant to be carried out the data modification of local local copy fully on the duplicate;
Said renewal behaviour is meant the data modification of complete duplicate is carried out on local local copy.
The conforming asynchronous method that collects of aforesaid maintenance data base duplicate is characterized in that: in said step 3), local copy is only revised at local node, and modification is committed to complete duplicate with local copy after accomplishing.
The conforming asynchronous method that collects of aforesaid maintenance data base duplicate is characterized in that: in said step 2) in, duplicate is only revised at local node fully, and modification need not submitted to after accomplishing.
The conforming asynchronous method that collects of aforesaid maintenance data base duplicate; It is characterized in that: submitting to complete duplicate and when complete duplicate upgrades; Carry out data check; If find to exist conflicting data to stop and the current submit operation of rollback or renewal operation, pop-up window operator notified simultaneously.
The conforming asynchronous method that collects of aforesaid maintenance data base duplicate is characterized in that: in said step 2) and step 3) in, optimize the triggering logical relation in the database, make the triggering logical equivalence of insert, update, delete unified.
The conforming asynchronous method that collects of aforesaid maintenance data base duplicate; It is characterized in that: in said step 2) and step 3) in; Increasing the attribute that is used for the data of description version change in the relation that produces by using, comprising: tuple creation-time, first creation node, tuple modification time, tuple are revised node, tuple deleted marker, tuple deletion time and tuple deletion node.
The conforming asynchronous method that collects of aforesaid maintenance data base duplicate; It is characterized in that: non-0 this tuple of expression of tuple deleted marker attribute is deleted; The tuple deleted marker is as the associating major key of relation, if the value of intrafascicular approximately other row of major key is identical, then delete flag adds up since 1.
The conforming asynchronous method that collects of aforesaid maintenance data base duplicate is characterized in that: the data difference of copy and local copy is different in nature relatively fully when upgrading operation with submit operation, in conjunction with the processing that conflicts of tuple running time.
The conforming asynchronous method that collects of aforesaid maintenance data base duplicate; It is characterized in that: in said step 3); Local copy was updated to earlier before revising local data and the complete the same versions of data of duplicate, and local copy is submitted to complete duplicate after accomplishing and revising in time.
The present invention proposes the notion of data duplicate grade:, the data duplicate is divided into two kinds of complete duplicate and local copy according to the coverage of data duplicate to total data.Fully comprised the overall situation all are centralized, the partition type data of redundance type data and this node for duplicate; Local copy comprises the partition type data of redundance type data and this node.
Local copy is only revised at local node, and modification is committed to complete duplicate with local copy after accomplishing, and other nodes can upgrade the data of having submitted to from complete duplicate.Merge from the redundance type data of local copy submission and the redundance type data the complete duplicate; The partition type data are not submitted to.
Duplicate is only revised at local node fully; Need not submit to after revising completion; Redundance type data wherein can be updated directly into local copy when needed, and local copy should Update Information from complete duplicate before once revising beginning, and after accomplishing modification, in time is committed to complete duplicate.
Submitting to complete duplicate and when complete duplicate upgrades, doing data check, in case find to exist conflicting data just to stop and the current submission of rollback or upgrade operation, pop-up window operator notified simultaneously.
The beneficial effect that the present invention reached:
Than the offline synchronization method, the asynchronous method of collecting that the present invention proposes can be supported the concurrent modification of multiple database, has overcome its dependence to dump file simultaneously.Than the online method for synchronous of realizing through application software; The asynchronous method of collecting that the present invention proposes greatly reduces the dependence to network stabilization; All the time all stablize from requiring network; Be reduced to and only require and before revising beginning, upgrade and revise that to accomplish the back stable when submitting to, and can in time detect the inconsistent situation of the data that existed and notify at once, effectively prevent the inconsistent scope continuation of data expansion to the operator.
Description of drawings
Fig. 1 is the conforming asynchronous process flow diagram that collects method of maintenance data base duplicate of the present invention.
Embodiment
The asynchronous realization that collects method that the present invention proposes mainly comprises 6 steps:
Step 1: the data in the database are cut apart, and according to demands of applications, model data are carried out relative degree/tuple level by following 4 kinds, perhaps horizontal/vertical/compound cutting apart:
1. only be stored in the data in the complete duplicate, this part data is referred to as centralized data;
2. only be stored in a certain local copy, this part data is only preserved portion in the overall situation, and this part data is referred to as the partition type data;
3. be stored in complete duplicate and each part local copy, and in all above-mentioned duplicates, all require the data that are consistent, this part data is referred to as the redundance type data;
4. be stored in the data in local local copy and the complete duplicate.
Only node has requirements for access to first kind of data at complete duplicate place; Second kind of data only has requirements for access at this local copy place node, so these two kinds of data need not carried out consistency maintenance, the third data all have requirements for access at complete duplicate and all local copy place nodes; It promptly possibly be certain common data commonly used; This is the part the highest to coherence request, and the 4th kind of data are common in the have hub-and-spoke configuration practical applications of (being center-minute site type structure), data local local copy with in the duplicate requirements for access is arranged fully; Do not need visit at other local copy place nodes; But other local nodes are duplicated in this part data commentaries on classics also can not produce any influence,, adopt identical disposal route so can conclude in the redundance type data to the data consistance.
Step 2: the definition submit operation is operated with upgrading:
Submit operation: the data modification of local local copy is being carried out on the duplicate fully;
Upgrade operation: the data modification of complete duplicate is carried out on local local copy.
Step 3: the content difference of more local local copy and the complete duplicate of far-end:
Because submission and renewal operation are all carried out on the node of local copy place, so local copy is local, complete duplicate is a far-end.Successively the identical relation in the complete duplicate of local local copy and far-end is compared, 4 kinds of results possibly occur: " coupling ", " disappearance ", " exceeding ", " difference ", like table 1:
The table as a result that table 1 data-base content relatively possibly occur
| ? | The local copy Major key | Complete duplicate Major key | The record attribute row |
| Coupling | Exist | Exist | Consistent |
| Disappearance | Exist | There is not (or having deleted) | ? |
| Exceed | There is not (or having deleted) | Exist | ? |
| Difference | Exist | Exist | Inconsistent |
Step 4: the triggering logic between optimum relations
In the database of real application systems, can there be the logical relation of some between relation and the relation, this relation generally realizes through the triggering logic of database.This step is to optimize these to trigger logical relation, and the triggering unified logic of insert, update, delete is got up.For example when update concerns the record of A, can trigger and in concern B, insert new record if a certain Column Properties is put 1, in concerning A, just must detect whether these row are 1 during one of insert so, 1 also in concerning B, insert respective record if be; In like manner, the deletion action for update causes also will take in when carrying out insert and delete, makes being kept perfectly property of logic and the consistance of Insert, update, delete.
Step 5: in relation, increase the control information attribute:
In order to have described the state of tuple in the relation, need be by using some attributes of extra interpolation in the relation that produces, these attributes comprise: the tuple creation-time; Unit's creation node, the tuple modification time, tuple is revised node; The tuple deleted marker, tuple deletion time, tuple deletion node.Wherein, to be used for recording operation be in the node at that duplicate place, to carry out to first creation/modification/deletion node.Non-0 this tuple of expression of tuple deleted marker attribute is deleted, and the tuple deleted marker is as the associating major key of relation, if the value of intrafascicular approximately other row of major key is identical, then delete flag adds up since 1.For example: alternately carry out repeatedly and insert and sweep equipment number is 100 tuple 3 times, then the delete flag attribute of 3 tuples is respectively 1,2,3.Owing to when carrying out deletion action, being not really tuple to be deleted, be changed to non-0 value but will delete first group mark, so can produce unnecessary tuple in the relation, these tuples can be unified deletion behind once overall consistency maintenance EO.
Step 6: the conflict when submission and renewal is handled:
Carrying out submit operation and upgrading in the process of operating, can skip for the tuple of having mated; For lack, exceed, the situation of difference needs to be treated differently as follows.
During renewal: for " disappearance "; The deletion time of more complete duplicate and the access time in the local copy (creation-time or recently modification time) are if the deletion time gap current time more closely then delete tuple in the local copy (is non-0 value with the deleted marker position).For " exceeding ", access time in the more complete duplicate and the deletion time in the local copy, if the access time apart from the current time more closely then in local copy, increase respective tuple.For " difference ", in the more complete duplicate with local copy in access time, if the access time fully in the duplicate is nearer then replace the tuple in the local copy with the tuple in the complete duplicate apart from the current time.If above-mentioned condition does not satisfy then keeps present situation, do not change the data in the local copy.
During submit operation: for " disappearance ", deletion time in the more complete duplicate and the access time in the local copy (creation-time or recently modification time), if the access time apart from the current time more closely then adding respective tuple in the duplicate fully.For " exceeding ", access time in the more complete duplicate and the deletion time in the local copy are if the deletion time gap current time more closely then delete tuple in the complete duplicate.For " difference ", in the more complete duplicate with local copy in access time, if the access time in the local copy is nearer then replace the tuple in the complete duplicate with the tuple in the local copy apart from the current time.Submit failure to if above-mentioned condition does not satisfy, the versions of data in the pop-up window prompting local copy is too outmoded, need be updated to latest edition and carry out data modification again.
The asynchronous method that collects that the present invention proposes; In the process of practical implementation; All local copy should be updated to earlier before revising local data and the complete the same versions of data of duplicate, and are same, after local copy is accomplished modification; Also should submit to complete duplicate in time, can reduce like this and submit unsuccessful occurrence probability to.
Recommended flowsheet when local copy is carried out data modification each time is: carry out the data à that the version à that Updates Information revises local local copy and submit the data of revising to complete duplicate to; Carrying out data modification at complete duplicate need not upgrade and submit to.
Except that the foregoing description, all employings are equal to the technical scheme that form obtained of replacement or equivalent transformation, all drop within protection scope of the present invention.
Claims (9)
1. the conforming asynchronous method that collects of maintenance data base duplicate is characterized in that, may further comprise the steps:
1) database otherness duplicate is divided into two types of complete duplicate and local copy, according to the requirement of using data is divided into sliver and leaves in two types of data duplicates;
2) relatively find out the variance data in complete duplicate and the local copy through data-base content, before revising local data, carry out and upgrade operation, from complete duplicate to the local copy synchrodata;
3) accomplish back execution submit operation revising local data, from local copy to complete duplicate synchrodata;
Said complete duplicate comprises the overall situation, and all are centralized, the partition type data of redundance type data and this node; Local copy comprises the partition type data of redundance type data and this node;
Said submit operation is meant to be carried out the data modification of local local copy fully on the duplicate;
Said renewal behaviour is meant the data modification of complete duplicate is carried out on local local copy.
2. the conforming asynchronous method that collects of maintenance data base duplicate according to claim 1 is characterized in that: in said step 3), local copy is only revised at local node, and modification is committed to complete duplicate with local copy after accomplishing.
3. the conforming asynchronous method that collects of maintenance data base duplicate according to claim 1 is characterized in that: in said step 2) in, duplicate is only revised at local node fully, and modification need not submitted to after accomplishing.
4. the conforming asynchronous method that collects of maintenance data base duplicate according to claim 1; It is characterized in that: submitting to complete duplicate and when complete duplicate upgrades; Carry out data check; If find to exist conflicting data to stop and the current submit operation of rollback or renewal operation, pop-up window operator notified simultaneously.
5. the conforming asynchronous method that collects of maintenance data base duplicate according to claim 1; It is characterized in that: in said step 2) and step 3) in; Optimize the triggering logical relation in the database, make the triggering logical equivalence of insert, update, delete unified.
6. the conforming asynchronous method that collects of maintenance data base duplicate according to claim 1; It is characterized in that: in said step 2) and step 3) in; Increasing the attribute that is used for the data of description version change in the relation that produces by using, comprising: tuple creation-time, first creation node, tuple modification time, tuple are revised node, tuple deleted marker, tuple deletion time and tuple deletion node.
7. the conforming asynchronous method that collects of maintenance data base duplicate according to claim 6; It is characterized in that: non-0 this tuple of expression of tuple deleted marker attribute is deleted; The tuple deleted marker is as the associating major key of relation; If the value of intrafascicular approximately other row of major key is identical, then delete flag adds up since 1.
8. the conforming asynchronous method that collects of maintenance data base duplicate according to claim 1 is characterized in that: the data difference of copy and local copy is different in nature relatively fully when upgrading operation with submit operation, in conjunction with the processing that conflicts of tuple running time.
9. the conforming asynchronous method that collects of maintenance data base duplicate according to claim 1; It is characterized in that: in said step 3); Local copy was updated to earlier before revising local data and the complete the same versions of data of duplicate, and local copy is submitted to complete duplicate after accomplishing and revising in time.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 201110367105 CN102402600B (en) | 2011-11-18 | 2011-11-18 | Asynchronous collecting method for maintaining consistency of database replicas |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 201110367105 CN102402600B (en) | 2011-11-18 | 2011-11-18 | Asynchronous collecting method for maintaining consistency of database replicas |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102402600A true CN102402600A (en) | 2012-04-04 |
| CN102402600B CN102402600B (en) | 2013-07-31 |
Family
ID=45884800
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN 201110367105 Active CN102402600B (en) | 2011-11-18 | 2011-11-18 | Asynchronous collecting method for maintaining consistency of database replicas |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102402600B (en) |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103020149A (en) * | 2012-11-22 | 2013-04-03 | 用友软件股份有限公司 | Shared data updating device and shared data updating method |
| CN104298769A (en) * | 2014-10-29 | 2015-01-21 | 北京思特奇信息技术股份有限公司 | System and method for synchronizing discrepant data of common domain between databases |
| CN106055353A (en) * | 2016-05-23 | 2016-10-26 | 北京小米移动软件有限公司 | Data update method and apparatus |
| CN106559225A (en) * | 2015-09-24 | 2017-04-05 | 百度在线网络技术（北京）有限公司 | The method and apparatus of data calibration |
| CN104216830B (en) * | 2014-09-01 | 2017-05-10 | 广州供电局有限公司 | Method and system for detecting consistency of equipment software |
| CN107609048A (en) * | 2017-08-18 | 2018-01-19 | 中国人民大学 | A kind of method for postponing unique constraint |
| CN108038140A (en) * | 2017-11-23 | 2018-05-15 | 广东岭南通股份有限公司 | Traffic all-purpose card transaction data full dose duplicate checking method and system |
| CN111625601A (en) * | 2020-05-27 | 2020-09-04 | 北京字节跳动网络技术有限公司 | Data writing method and device, computer equipment and storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7177866B2 (en) * | 2001-03-16 | 2007-02-13 | Gravic, Inc. | Asynchronous coordinated commit replication and dual write with replication transmission and locking of target database on updates only |
| CN101488148A (en) * | 2009-02-25 | 2009-07-22 | 浪潮集团山东通用软件有限公司 | Data compilation method in multiple databases |
| CN101826073A (en) * | 2009-03-06 | 2010-09-08 | 华为技术有限公司 | Synchronous method, apparatus and system for distributed database |
-
2011
- 2011-11-18 CN CN 201110367105 patent/CN102402600B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7177866B2 (en) * | 2001-03-16 | 2007-02-13 | Gravic, Inc. | Asynchronous coordinated commit replication and dual write with replication transmission and locking of target database on updates only |
| CN101488148A (en) * | 2009-02-25 | 2009-07-22 | 浪潮集团山东通用软件有限公司 | Data compilation method in multiple databases |
| CN101826073A (en) * | 2009-03-06 | 2010-09-08 | 华为技术有限公司 | Synchronous method, apparatus and system for distributed database |
Cited By (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103020149B (en) * | 2012-11-22 | 2016-01-20 | 用友网络科技股份有限公司 | Share data update apparatus and shared data-updating method |
| CN103020149A (en) * | 2012-11-22 | 2013-04-03 | 用友软件股份有限公司 | Shared data updating device and shared data updating method |
| CN104216830B (en) * | 2014-09-01 | 2017-05-10 | 广州供电局有限公司 | Method and system for detecting consistency of equipment software |
| CN104298769B (en) * | 2014-10-29 | 2017-06-13 | 北京思特奇信息技术股份有限公司 | Domain variance data synchronization system and method are had between a kind of database |
| CN104298769A (en) * | 2014-10-29 | 2015-01-21 | 北京思特奇信息技术股份有限公司 | System and method for synchronizing discrepant data of common domain between databases |
| CN106559225A (en) * | 2015-09-24 | 2017-04-05 | 百度在线网络技术（北京）有限公司 | The method and apparatus of data calibration |
| CN106055353A (en) * | 2016-05-23 | 2016-10-26 | 北京小米移动软件有限公司 | Data update method and apparatus |
| CN106055353B (en) * | 2016-05-23 | 2019-03-29 | 北京小米移动软件有限公司 | Data-updating method and device |
| CN107609048A (en) * | 2017-08-18 | 2018-01-19 | 中国人民大学 | A kind of method for postponing unique constraint |
| CN107609048B (en) * | 2017-08-18 | 2020-09-04 | 中国人民大学 | Method capable of delaying unique constraint |
| CN108038140A (en) * | 2017-11-23 | 2018-05-15 | 广东岭南通股份有限公司 | Traffic all-purpose card transaction data full dose duplicate checking method and system |
| CN111625601A (en) * | 2020-05-27 | 2020-09-04 | 北京字节跳动网络技术有限公司 | Data writing method and device, computer equipment and storage medium |
| CN111625601B (en) * | 2020-05-27 | 2023-03-14 | 北京火山引擎科技有限公司 | Data writing method and device, computer equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102402600B (en) | 2013-07-31 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102402600B (en) | Asynchronous collecting method for maintaining consistency of database replicas | |
| CN101334797B (en) | Distributed file systems and its data block consistency managing method | |
| EP3304356B1 (en) | Table partitioning within distributed database systems | |
| CN105359099B (en) | Index update pipeline | |
| US20200050387A1 (en) | Fast migration of metadata | |
| CN108369601B (en) | Promoting attributes in relational structured data | |
| EP3391244B1 (en) | Replication control among redundant data centers | |
| CN103455557B (en) | A kind of structural data synchronous method based on daily record | |
| CN101577735A (en) | Method, device and system for taking over fault metadata server | |
| CN108153804B (en) | Metadata log updating method for symmetric distributed file system | |
| EP3575968A1 (en) | Method and device for synchronizing active transaction lists | |
| CN103034739A (en) | Distributed memory system and updating and querying method thereof | |
| US10235406B2 (en) | Reminder processing of structured data records among partitioned data storage spaces | |
| WO2011084987A1 (en) | Traversal-free rapid data transfer | |
| CN106802905B (en) | Collaborative data exchange method of isomorphic PLM system | |
| EP3391249A1 (en) | Replication of structured data records among partitioned data storage spaces | |
| CN103345502A (en) | Transaction processing method and system of distributed type database | |
| CN111917834A (en) | Data synchronization method and device, storage medium and computer equipment | |
| US7020656B1 (en) | Partition exchange loading technique for fast addition of data to a data warehousing system | |
| CN110727733B (en) | Master-slave server system and data synchronization method | |
| US20070220420A1 (en) | System and method for efficient maintenance of indexes for XML files | |
| CN113656384B (en) | Data processing method, distributed database system, electronic device and storage medium | |
| CN103778176B (en) | For the system of data long term archival, method and computer usable medium in MES system | |
| CN101046822A (en) | Centralized management of data nodes | |
| CN114153809A (en) | Parallel real-time incremental statistic method based on database logs |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| ASS | Succession or assignment of patent right |
Owner name: NARI NANJING CONTROL SYSTEM LTD. Effective date: 20141205 |
|
| C41 | Transfer of patent application or patent right or utility model | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20141205 Address after: High road high tech Development Zone Nanjing city Jiangsu province 210061 No. 20 Patentee after: NARI Technology Development Co., Ltd. Patentee after: SGCC NARI Nanjing Control System Co., Ltd. Address before: High road high tech Development Zone Nanjing city Jiangsu province 210061 No. 20 Patentee before: NARI Technology Development Co., Ltd. |
|
| CB03 | Change of inventor or designer information |
Inventor after: Chen Tianhao Inventor after: Liang Yi Inventor after: Fang Jun Inventor after: Zhang Saiqiao Inventor after: Shi Qi Inventor after: Liu Jiabao Inventor after: Xu Shiming Inventor after: Li Tianyang Inventor before: Chen Tianhao Inventor before: Liang Yi Inventor before: Fang Jun Inventor before: Zhang Saiqiao Inventor before: Shi Qi Inventor before: Liu Jiabao |
|
| COR | Change of bibliographic data |