US7359926B1 - System for optimization of database replication/synchronization - Google Patents

System for optimization of database replication/synchronization Download PDF

Info

Publication number
US7359926B1
US7359926B1 US10/367,250 US36725003A US7359926B1 US 7359926 B1 US7359926 B1 US 7359926B1 US 36725003 A US36725003 A US 36725003A US 7359926 B1 US7359926 B1 US 7359926B1
Authority
US
United States
Prior art keywords
database object
database
computer
alteration
unique identifier
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.)
Active, expires
Application number
US10/367,250
Inventor
Thomas P. Yohe
Brian C. Morris
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Comtech EF Data Corp
Original Assignee
Stampede Technologies Inc
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Stampede Technologies Inc filed Critical Stampede Technologies Inc
Priority to US10/367,250 priority Critical patent/US7359926B1/en
Assigned to STAMPEDE TECHNOLOGIES, INC. reassignment STAMPEDE TECHNOLOGIES, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: YOHE, THOMAS P., MORRIS, BRIAN C.
Application granted granted Critical
Publication of US7359926B1 publication Critical patent/US7359926B1/en
Assigned to COMTECH EF DATA CORPORATION reassignment COMTECH EF DATA CORPORATION ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: STAMPEDE TECHNOLOGIES, INC.
Assigned to CITIBANK N.A., AS ADMINISTRATIVE AGENT reassignment CITIBANK N.A., AS ADMINISTRATIVE AGENT SECURITY AGREEMENT Assignors: COMTECH EF DATA CORP., COMTECH MOBILE DATACOM CORPORATION, COMTECH XICOM TECHNOLOGY, INC., TELECOMMUNICATION SYSTEMS, INC.
Active legal-status Critical Current
Adjusted expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/27Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00Data processing: database and file management or data structures
    • Y10S707/99951File or database maintenance
    • Y10S707/99952Coherency, e.g. same view to multiple users
    • Y10S707/99953Recoverability
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00Data processing: database and file management or data structures
    • Y10S707/99951File or database maintenance
    • Y10S707/99952Coherency, e.g. same view to multiple users
    • Y10S707/99955Archiving or backup

Definitions

  • the present invention relates to a system for optimizing database replication/synchronization.
  • Database replication is a process for synchronizing data updates between databases in different locations.
  • Database replication includes transferring updates between servers so that two or more copies of the database remain synchronized.
  • Each copy of the database is called a replica, and each contains a common set of documents (Tables, views, forms, reports, macros, and modules).
  • Database servers can exchange updates of data or replicable objects to keep replicas synchronized. This exchange is called replication.
  • Database replications allow users at different locations to work on their own copy and share and synchronize their changes. In the case of an application for multiple users, database replication can improve the way users share data.
  • Each member of the replica set contains a common set of replicable objects.
  • Each replica can also contain local objects, in other words, objects that are synchronized during replication and objects that remain on the local computer and are not replicated. This allows one copy of a database to be customized for a specific group or users while still synchronizing common data with other members in the replica set.
  • Replication is common for accessing data, wherein a replica of a database on a remote computer connects a server computer so that synchronization of changes made to the replica on the remote computer can be made with changes on a database.
  • One traditional approach to replication/synchronization would be to create a single database that contains both the data and the objects, and then make replicas of the database for each computer.
  • database replication can solve many of the problems inherent in distributed-database processing, current replication techniques require improvement due to inherent inefficiencies.
  • the replication can be time consuming and costly in cases where there are a large number of updates where the updates consist of a transformation of the replicable objects (an example of a transform would be to convert the object into a compressed format), or applications that require frequent updates of existing records in different replicas are likely to have more record conflicts than applications that simply insert new records in a database, or applications with many record conflicts require more administrative time because the conflicts must be resolved manually.
  • the present invention fulfills this and other needs.
  • the present invention is directed to a system for optimization of database replication/synchronization.
  • the system includes a first computer-based device having software thereon with means for obtaining a state of condition a database object and associating a unique identifier with such database object, means for altering form of the data in the database object and associating another unique identifier with such altered database object, and means for determining the database object using the unique identifiers.
  • the alteration can include a transformation operation, such as compression, expansion, encryption, de-encryption, conversion, de-conversion.
  • the unique identifier can be a sequence number and modification time, for example.
  • the invention presumes the installation of the software be installed on both computers. A method employing the above is also provided.
  • FIG. 1 is a block diagram of the state of the prior art.
  • FIG. 2 is a block diagram of the present invention.
  • FIG. 3 is a flow chart of another operation of the present invention.
  • the system 10 includes a computer which is capable of running standard operating system such as Windows, Linux, or Unix.
  • the system 10 includes a conventional computer 12 having a central processor (CPU) 14 , random memory 16 , permanent memory 18 (e.g., hard or fixed disk, optical disk, magneto-optical disk, or flash memory), and can include a keyboard 20 , a mouse 22 (or like pointing device), a clock 24 and a display or screen device 26 .
  • Processor 14 is operably associated with memory 16 for storing frequently accessed information.
  • One or more input/output device(s) 28 such as a printer can be included.
  • the CPU 12 includes a communication link 30 which can be a LAN, WAN or modem connection, for example.
  • Operably residing on the CPU 12 is operating software 36 as is known in the art.
  • the operating software 36 is preferably stored in memory 18 , and includes a one or more application programs, such as client application software or programs loaded thereon which can execute in a manner as is known in the art. Additionally, the CPU 12 can include one or more applications loaded thereon, such as Microsoft Outlook® or Lotus Notes®.
  • the present invention further provides for replication/synchronization software 38 thereon having the ability to obtain a state of condition a database object 40 stored in memory 18 and associating a unique identifier 41 with such database object 40 .
  • the software 38 is further capable of altering the form of the data 40 thus providing database object 40 ′ and associating another unique identifier 41 ′ with such altered database object 40 ′ which is also stored in the memory 18 .
  • the software 38 is thereafter capable of determining whether the database object to be replicated is either in an unaltered form 40 or an altered form 40 ′ using the unique identifiers 41 and 41 ′.
  • Another feature of the software 38 is that it is capable of receiving a replication request from another computer 112 , e.g., remote pc, for one of the database objects 40 or 40 ′, wherein the request contains one of the unique identifiers 41 or 41 ′, for example, and comparatively equating to one of the identifiers on the first computer 12 .
  • the computer (CPU) 112 has a central processor 114 , random memory 116 , permanent memory 118 , and can include a keyboard 120 , a mouse 122 , a clock 124 and a display or screen device 126 , input/output device(s) 128 , and a communication link 130 , for example.
  • operating software 136 residing on the CPU 112 is operating software 136 and includes one or more applications as above and complementary replication/synchronization software 138 which operates in a manner as described for replication/synchronization software 38 herein.
  • Replication/synchronization software 38 is capable of sending (or receiving) either an instruction to replication/synchronization software 138 on computer 112 to perform a like alteration on the database object or to send (or receive) the changes to the database object.
  • the alteration can include a transformation operation, such as compression, expansion, encryption, de-encryption, conversion, de-conversion.
  • the unique identifier can be a sequence number and modification time should be unique for this data, for example.
  • the database object 40 can be compressed to provide a compressed database object 40 ′ which is given a unique identifier 41 ′.
  • the software 38 stores the file in a compressed format and provides for a decompression utility in order to access the compressed database object 40 .
  • the internal structure of the compressed database object 40 ′ is not maintained in a manner which can necessarily be used to for a replication process between computers 12 and 112 .
  • An objective of this invention is to allow the replication/synchronization process to proceed when possible without the need for transferring the data between computers 12 and 112 . This significantly reduces the traffic of over the network in which these computers are commonly employed. This is enabled by the use of the unique identifiers 41 and 41 ′ which are created and used by software 38 and 138 .
  • the internal format of the database objects can be dynamically modified in a manner so that it replicates without having to invoke traditional industry standard replication techniques. This reduces the time and network bandwidth consuming step.
  • FIG. 3 depicts a flow chart of the replication/synchronization system 38 / 138 .
  • Replication/synchronization software (RSS) 38 / 138 determines 300 the status of a database object to unaltered or altered. If altered, RSS 38 / 138 associates 302 another unique identifier 41 ′ with database object 40 ′. If unaltered. RSS 38 / 138 associates 304 a unique identifier 41 with database object 40 .
  • RSS 38 receives 306 a replication request from RSS 138 .
  • RSS 38 uses 308 unique identifier 41 / 41 ′ to determine whether it is associated with database object 40 / 40 ′. If yes, RSS 38 sends 310 RSS 138 an instruction to perform same alteration using same application software. If no, RSS 38 sends 312 copy of requested database object using conventional replication.
  • the present invention is not intended to be limited to any particular architecture, application or particular environment. However, by way of example, the present invention will describe the implementation of the invention in a Lotus Notes/Domino environment. Persons skilled in the art will find that the system and methods of the present invention may be advantageously applied to a variety of other systems and application software, including database management systems, e-mail software, web browsers or any application where the existence of a file attachment is denoted graphically, and the like.

Abstract

A system for optimization of database replication/synchronization includes a first computer-based device having software thereon for obtaining a state of condition a database object and associating a unique identifier with such database object, for altering form of the data and associating another unique identifier with such altered database object, and for determining the database object using the unique identifiers. The system can receive a replication request for updating data from a second computer for a database object on the second computer wherein the request contains a unique identifier comparatively equating to one of the identifiers on the first computer and sends either an instruction to second computer to perform a like alteration on the data or to send the changes to the database object.

Description

BACKGROUND OF THE INVENTION
1. Field of the Invention
The present invention relates to a system for optimizing database replication/synchronization.
2. Related Art
Database replication is a process for synchronizing data updates between databases in different locations. Database replication includes transferring updates between servers so that two or more copies of the database remain synchronized. Each copy of the database is called a replica, and each contains a common set of documents (Tables, views, forms, reports, macros, and modules). Database servers can exchange updates of data or replicable objects to keep replicas synchronized. This exchange is called replication. Database replications allow users at different locations to work on their own copy and share and synchronize their changes. In the case of an application for multiple users, database replication can improve the way users share data.
Each member of the replica set contains a common set of replicable objects. Each replica can also contain local objects, in other words, objects that are synchronized during replication and objects that remain on the local computer and are not replicated. This allows one copy of a database to be customized for a specific group or users while still synchronizing common data with other members in the replica set.
Replication is common for accessing data, wherein a replica of a database on a remote computer connects a server computer so that synchronization of changes made to the replica on the remote computer can be made with changes on a database. One traditional approach to replication/synchronization would be to create a single database that contains both the data and the objects, and then make replicas of the database for each computer.
Although database replication can solve many of the problems inherent in distributed-database processing, current replication techniques require improvement due to inherent inefficiencies. For example, the replication can be time consuming and costly in cases where there are a large number of updates where the updates consist of a transformation of the replicable objects (an example of a transform would be to convert the object into a compressed format), or applications that require frequent updates of existing records in different replicas are likely to have more record conflicts than applications that simply insert new records in a database, or applications with many record conflicts require more administrative time because the conflicts must be resolved manually.
What is needed is an improved replication/synchronization process which decreases the computer usage time and cost. The present invention fulfills this and other needs.
BRIEF SUMMARY OF THE INVENTION
It is an object to improve the database replication/synchronization.
It is another object to accelerate replication/synchronization.
It is still another object to provide a replication/synchronization system which can be employed on a variety of platforms and interfaces with various programs.
Accordingly, the present invention is directed to a system for optimization of database replication/synchronization. The system includes a first computer-based device having software thereon with means for obtaining a state of condition a database object and associating a unique identifier with such database object, means for altering form of the data in the database object and associating another unique identifier with such altered database object, and means for determining the database object using the unique identifiers. Also, provided are means for receiving a replication request from a second computer for updated data relating to a database object thereon and containing a unique identifier and comparatively equating to one of the identifiers on the first computer and for sending either an instruction to the second computer to perform a like alteration on the data or to send the changes to the database object. The alteration can include a transformation operation, such as compression, expansion, encryption, de-encryption, conversion, de-conversion. The unique identifier can be a sequence number and modification time, for example. The invention presumes the installation of the software be installed on both computers. A method employing the above is also provided.
Other objects and advantages will be readily apparent to those skilled in the art upon viewing the drawings and reading the detailed description hereafter.
BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 is a block diagram of the state of the prior art.
FIG. 2 is a block diagram of the present invention.
FIG. 3 is a flow chart of another operation of the present invention.
DETAILED DESCRIPTION OF THE INVENTION
Referring now to the drawings, the system of the preferred embodiment of the present invention is generally referred to by the numeral 10. The system 10 includes a computer which is capable of running standard operating system such as Windows, Linux, or Unix.
The system 10 includes a conventional computer 12 having a central processor (CPU) 14, random memory 16, permanent memory 18 (e.g., hard or fixed disk, optical disk, magneto-optical disk, or flash memory), and can include a keyboard 20, a mouse 22 (or like pointing device), a clock 24 and a display or screen device 26. Processor 14 is operably associated with memory 16 for storing frequently accessed information. One or more input/output device(s) 28, such as a printer can be included. The CPU 12 includes a communication link 30 which can be a LAN, WAN or modem connection, for example.
Operably residing on the CPU 12 is operating software 36 as is known in the art. The operating software 36 is preferably stored in memory 18, and includes a one or more application programs, such as client application software or programs loaded thereon which can execute in a manner as is known in the art. Additionally, the CPU 12 can include one or more applications loaded thereon, such as Microsoft Outlook® or Lotus Notes®.
The present invention further provides for replication/synchronization software 38 thereon having the ability to obtain a state of condition a database object 40 stored in memory 18 and associating a unique identifier 41 with such database object 40. The software 38 is further capable of altering the form of the data 40 thus providing database object 40′ and associating another unique identifier 41′ with such altered database object 40′ which is also stored in the memory 18.
The software 38 is thereafter capable of determining whether the database object to be replicated is either in an unaltered form 40 or an altered form 40′ using the unique identifiers 41 and 41′. Another feature of the software 38 is that it is capable of receiving a replication request from another computer 112, e.g., remote pc, for one of the database objects 40 or 40′, wherein the request contains one of the unique identifiers 41 or 41′, for example, and comparatively equating to one of the identifiers on the first computer 12. Similarly, the computer (CPU) 112 has a central processor 114, random memory 116, permanent memory 118, and can include a keyboard 120, a mouse 122, a clock 124 and a display or screen device 126, input/output device(s) 128, and a communication link 130, for example. Similarly, residing on the CPU 112 is operating software 136 and includes one or more applications as above and complementary replication/synchronization software 138 which operates in a manner as described for replication/synchronization software 38 herein.
Replication/synchronization software 38 is capable of sending (or receiving) either an instruction to replication/synchronization software 138 on computer 112 to perform a like alteration on the database object or to send (or receive) the changes to the database object. The alteration can include a transformation operation, such as compression, expansion, encryption, de-encryption, conversion, de-conversion. The unique identifier can be a sequence number and modification time should be unique for this data, for example. For example, in the case of compression, the database object 40 can be compressed to provide a compressed database object 40′ which is given a unique identifier 41′. The software 38 stores the file in a compressed format and provides for a decompression utility in order to access the compressed database object 40.
Conventionally, the internal structure of the compressed database object 40′ is not maintained in a manner which can necessarily be used to for a replication process between computers 12 and 112. An objective of this invention is to allow the replication/synchronization process to proceed when possible without the need for transferring the data between computers 12 and 112. This significantly reduces the traffic of over the network in which these computers are commonly employed. This is enabled by the use of the unique identifiers 41 and 41′ which are created and used by software 38 and 138.
With the instant invention, the internal format of the database objects can be dynamically modified in a manner so that it replicates without having to invoke traditional industry standard replication techniques. This reduces the time and network bandwidth consuming step.
FIG. 3 depicts a flow chart of the replication/synchronization system 38/138. Replication/synchronization software (RSS) 38/138 determines 300 the status of a database object to unaltered or altered. If altered, RSS 38/138 associates 302 another unique identifier 41′ with database object 40′. If unaltered. RSS 38/138 associates 304 a unique identifier 41 with database object 40. RSS 38 receives 306 a replication request from RSS 138. RSS 38 uses 308 unique identifier 41/41′ to determine whether it is associated with database object 40/40′. If yes, RSS 38 sends 310 RSS 138 an instruction to perform same alteration using same application software. If no, RSS 38 sends 312 copy of requested database object using conventional replication.
The present invention is not intended to be limited to any particular architecture, application or particular environment. However, by way of example, the present invention will describe the implementation of the invention in a Lotus Notes/Domino environment. Persons skilled in the art will find that the system and methods of the present invention may be advantageously applied to a variety of other systems and application software, including database management systems, e-mail software, web browsers or any application where the existence of a file attachment is denoted graphically, and the like.
The above described embodiments are set forth by way of example and are not for the purpose of limiting the present invention. It will be readily apparent to those skilled in the art that obvious modifications, derivations and variations can be made to the embodiments without departing from the scope of the invention. Accordingly, the claims appended hereto should be read in their full scope including any such modifications, derivations and variations.

Claims (11)

1. A system for optimization of database replication/synchronization, including:
a first computer-based device having software thereon with means for associating a first unique identifier with a first database object;
means for performing a first alteration upon said first database object to provide an altered second database object and associating a second unique identifier with said altered second database object, wherein said first alteration includes a transformation operation comprising compression, expansion, encryption, de-encryption, conversion, and de-conversion;
means for determining said database objects to be replicated either in altered form or unaltered form using said unique identifiers; and
means for receiving a replication request for updating data for a third database object from a second computer based device containing a third unique identifier and comparatively equating said third unique identifier to one of said first and second identifiers and for sending an instruction to said second computer based device to perform said first alteration upon said third database object thereon to maintain said database objects in sync and for sending said requested updated data when said second computer lacks means for performing said first alteration.
2. The system of claim 1, wherein said unique identifier includes a sequence number.
3. The system of claim 1, wherein said second computer-based device has complementary software thereon with means for associating a third unique identifier with condition of said third database object thereon;
means for performing a second alteration upon said third database object to provide an altered fourth database object thereon and associating a fourth unique identifier with said fourth altered database object, wherein said second alteration includes a transformation operation comprising compression, expansion, encryption, de-encryption, conversion, and de-conversion determining said database object using said unique identifiers, and
means for receiving a replication request from said first computer for updating data and containing one of said first and second unique identifiers and comparatively equating to one of said other identifiers and for sending an instruction to said first computer based device to perform said second alteration upon data thereon to maintain said database objects in sync.
4. The system of claim 1, wherein said replication/synchronization is characterized to be performed transparent to a user.
5. A method for optimization of database replication/synchronization, including:
employing a first computer-based device having software thereon with means associating a first unique identifier with a first database object;
performing a first alteration upon said first database object to provide an altered second database object, wherein said first alteration includes a transformation operation comprising at least one of compression, expansion, encryption, de-encryption, conversion, and de-conversion;
associating a second unique identifier with said altered second database object;
determining said database objects to be replicated either in altered form or unaltered form using said unique identifiers; and
receiving a replication request for updating data for a third database object from a second computer containing a third unique identifier and comparatively equating said third unique identifier to one of said first and second identifiers and for sending an instruction to said second computer based device to perform said first alteration upon of said third database object thereon to maintain said database objects in sync and for sending said requested updated data when said second computer lacks means for performing said first alteration.
6. The method of claim 5, wherein said unique identifier includes a sequence number.
7. The method of claim 5, wherein said second computer-based device has complementary software thereon with and includes the step of associating a third unique identifier with said third database object thereon;
performing a second alteration upon said third database object to provide an altered fourth database object thereon and associating a fourth unique identifier with said fourth altered database object, wherein said second alteration includes a transformation operation comprising at least one of compression, expansion, encryption, de-encryption, conversion, and de-conversion;
determining said database objects to be replicated either in altered form or unaltered form using said unique identifiers; and
receiving a replication request from said first computer for updating data and containing one of said first and second unique identifiers and comparatively equating to one of said other identifiers and for sending an instruction to said first computer based device to perform said second alteration upon data thereon to maintain said database objects in sync.
8. The method of claim 5, wherein said replication/synchronization is characterized to be performed transparent to a user.
9. A system for optimization of database replication/synchronization, including:
a first computer-based device having software thereon with means for associating a first unique identifier with a first database object;
means for performing a first alteration upon said first database object to provide an altered second database object and associating a second unique identifier with said altered second database object, wherein said first alteration includes a transformation operation comprising at least one of compression, expansion, encryption, de-encryption, conversion, and de-conversion;
means for determining said database objects to be replicated either in altered form or unaltered form using said unique identifiers; and
means for receiving a replication request for updating data for a third database object from a second computer based device containing a third unique identifier and comparatively equating said third unique identifier to one of said first and second identifiers and for sending an instruction to said second computer based device to perform said first alteration upon said third database object thereon to maintain said database objects in sync and for sending said requested updated data when said second computer lacks means for performing said first alteration.
10. The system of claim 9, wherein said second computer-based device has complementary software thereon with means for associating a third unique identifier with said third database object thereon;
means for performing a second alteration upon said third database object to provide an altered fourth database object thereon and associating a fourth unique identifier with said fourth altered database object, wherein said second alteration includes a transformation operation comprising at least one of compression, expansion, encryption, de-encryption, conversion, and de-conversion determining said database object using said unique identifiers, and
means for receiving a replication request from said first computer for updating data and containing one of said first and second unique identifiers and comparatively equating to one of said other identifiers and for sending an instruction to said first computer based device to perform said second alteration upon data thereon to maintain said database objects in sync.
11. The system of claim 9, wherein said replication/synchronization is characterized to be performed transparent to a user.
US10/367,250 2003-02-13 2003-02-13 System for optimization of database replication/synchronization Active 2024-05-05 US7359926B1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US10/367,250 US7359926B1 (en) 2003-02-13 2003-02-13 System for optimization of database replication/synchronization

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US10/367,250 US7359926B1 (en) 2003-02-13 2003-02-13 System for optimization of database replication/synchronization

Publications (1)

Publication Number Publication Date
US7359926B1 true US7359926B1 (en) 2008-04-15

Family

ID=39281694

Family Applications (1)

Application Number Title Priority Date Filing Date
US10/367,250 Active 2024-05-05 US7359926B1 (en) 2003-02-13 2003-02-13 System for optimization of database replication/synchronization

Country Status (1)

Country Link
US (1) US7359926B1 (en)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080114816A1 (en) * 2006-11-10 2008-05-15 Sybase, Inc. Replication system with methodology for replicating database sequences
US20110066539A1 (en) * 2009-09-15 2011-03-17 Andrew Auerbach Method and System For Enhancing The Efficiency Of A Digitally Communicated Data Exchange
US20120233354A1 (en) * 2006-10-02 2012-09-13 Salesforce.Com, Inc. Method and system for synchronizing a server and an on-demand database service
US8495017B2 (en) * 2011-08-03 2013-07-23 Amadeus S.A.S. Method and system to maintain strong consistency of distributed replicated contents in a client/server system
CN106649577A (en) * 2016-11-17 2017-05-10 杭州沃趣科技股份有限公司 Method for detecting running state of synchronous software of Oracle database
US10402422B2 (en) * 2013-08-01 2019-09-03 OMS Software GMBH Method and system for synchronizing data

Citations (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5787262A (en) 1996-06-26 1998-07-28 Microsoft Corporation System and method for distributed conflict resolution between data objects replicated across a computer network
US5794253A (en) 1996-07-12 1998-08-11 Microsoft Corporation Time based expiration of data objects in a store and forward replication enterprise
US5864851A (en) 1997-04-14 1999-01-26 Lucent Technologies Inc. Method and system for managing replicated data with enhanced consistency and concurrency
US5999931A (en) 1997-10-17 1999-12-07 Lucent Technologies Inc. Concurrency control protocols for management of replicated data items in a distributed database system
US6049809A (en) 1996-10-30 2000-04-11 Microsoft Corporation Replication optimization system and method
US6163811A (en) 1998-10-21 2000-12-19 Wildseed, Limited Token based source file compression/decompression and its application
US6205481B1 (en) 1998-03-17 2001-03-20 Infolibria, Inc. Protocol for distributing fresh content among networked cache servers
US6253211B1 (en) 1997-07-26 2001-06-26 International Business Machines Corp. Replication tracking method and apparatus for a distributed data processing system
US6304882B1 (en) 1998-05-05 2001-10-16 Informix Software, Inc. Data replication system and method
US6318124B1 (en) 1999-08-23 2001-11-20 Alliedsignal Inc. Nanoporous silica treated with siloxane polymers for ULSI applications
US6345308B1 (en) 1998-02-27 2002-02-05 Kabushiki Kaisha Toshiba Network computer system and method for executing data synchronization process thereof
US6405219B2 (en) 1999-06-22 2002-06-11 F5 Networks, Inc. Method and system for automatically updating the version of a set of files stored on content servers
US6457011B1 (en) 1999-07-23 2002-09-24 Microsoft Corporation Method of updating a shared database in a computer network
US6516327B1 (en) 1998-12-24 2003-02-04 International Business Machines Corporation System and method for synchronizing data in multiple databases
US6889247B2 (en) * 1995-05-31 2005-05-03 Netscape Communications Corporation Method and apparatus for workgroup information replication

Patent Citations (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6889247B2 (en) * 1995-05-31 2005-05-03 Netscape Communications Corporation Method and apparatus for workgroup information replication
US5787262A (en) 1996-06-26 1998-07-28 Microsoft Corporation System and method for distributed conflict resolution between data objects replicated across a computer network
US5794253A (en) 1996-07-12 1998-08-11 Microsoft Corporation Time based expiration of data objects in a store and forward replication enterprise
US6049809A (en) 1996-10-30 2000-04-11 Microsoft Corporation Replication optimization system and method
US5864851A (en) 1997-04-14 1999-01-26 Lucent Technologies Inc. Method and system for managing replicated data with enhanced consistency and concurrency
US6253211B1 (en) 1997-07-26 2001-06-26 International Business Machines Corp. Replication tracking method and apparatus for a distributed data processing system
US5999931A (en) 1997-10-17 1999-12-07 Lucent Technologies Inc. Concurrency control protocols for management of replicated data items in a distributed database system
US6345308B1 (en) 1998-02-27 2002-02-05 Kabushiki Kaisha Toshiba Network computer system and method for executing data synchronization process thereof
US6205481B1 (en) 1998-03-17 2001-03-20 Infolibria, Inc. Protocol for distributing fresh content among networked cache servers
US6304882B1 (en) 1998-05-05 2001-10-16 Informix Software, Inc. Data replication system and method
US6163811A (en) 1998-10-21 2000-12-19 Wildseed, Limited Token based source file compression/decompression and its application
US6516327B1 (en) 1998-12-24 2003-02-04 International Business Machines Corporation System and method for synchronizing data in multiple databases
US6405219B2 (en) 1999-06-22 2002-06-11 F5 Networks, Inc. Method and system for automatically updating the version of a set of files stored on content servers
US6457011B1 (en) 1999-07-23 2002-09-24 Microsoft Corporation Method of updating a shared database in a computer network
US6318124B1 (en) 1999-08-23 2001-11-20 Alliedsignal Inc. Nanoporous silica treated with siloxane polymers for ULSI applications

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9854039B2 (en) 2006-10-02 2017-12-26 Salesforce.Com, Inc. Method and system for synchronizing a server and an on-demand database service
US20120233354A1 (en) * 2006-10-02 2012-09-13 Salesforce.Com, Inc. Method and system for synchronizing a server and an on-demand database service
US8762329B2 (en) * 2006-10-02 2014-06-24 Salesforce.Com, Inc. Method and system for synchronizing a server and an on-demand database service
US20080114816A1 (en) * 2006-11-10 2008-05-15 Sybase, Inc. Replication system with methodology for replicating database sequences
US7587435B2 (en) 2006-11-10 2009-09-08 Sybase, Inc. Replication system with methodology for replicating database sequences
US8538861B2 (en) 2009-09-15 2013-09-17 Auerbach Group Llc Use of adaptive and/or customized compression to enhance the efficiency of digital financial data exchanges
US8756149B2 (en) 2009-09-15 2014-06-17 Auerbach Group Llc Use of adaptive and/or customized compression to enhance the efficiency of digital data exchanges
US8321326B2 (en) 2009-09-15 2012-11-27 Auerbach Group Llc Method and system for enhancing the efficiency of a digitally communicated data exchange
US20110066539A1 (en) * 2009-09-15 2011-03-17 Andrew Auerbach Method and System For Enhancing The Efficiency Of A Digitally Communicated Data Exchange
US8495017B2 (en) * 2011-08-03 2013-07-23 Amadeus S.A.S. Method and system to maintain strong consistency of distributed replicated contents in a client/server system
US10402422B2 (en) * 2013-08-01 2019-09-03 OMS Software GMBH Method and system for synchronizing data
CN106649577A (en) * 2016-11-17 2017-05-10 杭州沃趣科技股份有限公司 Method for detecting running state of synchronous software of Oracle database
CN106649577B (en) * 2016-11-17 2020-02-07 杭州沃趣科技股份有限公司 Method for detecting running state of synchronous software of Oracle database

Similar Documents

Publication Publication Date Title
US6321236B1 (en) Distributing database differences corresponding to database change events made to a database table located on a server computer
US8170981B1 (en) Computer method and system for combining OLTP database and OLAP database environments
US7404011B2 (en) System and method for accessing different types of back end data stores
KR100592647B1 (en) System and method for a caching mechanism for a central synchronization server
US6983293B2 (en) Mid-tier-based conflict resolution method and system usable for message synchronization and replication
US7146614B1 (en) Computer directory system having an application integration driver infrastructure
EP1459213B1 (en) System and methods for asychronous synchronization
US20080034012A1 (en) Extending hierarchical synchronization scopes to non-hierarchical scenarios
US7672966B2 (en) Adding extrinsic data columns to an existing database schema using a temporary column pool
CN113535656B (en) Data access method, device, equipment and storage medium
US7523141B2 (en) Synchronization operations involving entity identifiers
US20030130999A1 (en) Dynamic information format conversion
US20020116467A1 (en) Method and apparatus for synchronizing an email client on a portable computer system with an email client on a desktop computer
US20050256907A1 (en) Systems and methods for the utilization of metadata for synchronization optimization
AU2004200462A1 (en) A method for managing multiple file states for replicated files
WO2012018424A2 (en) Mysql database heterogeneous log based replication
WO2011108695A1 (en) Parallel data processing system, parallel data processing method and program
US10133744B2 (en) Composite execution of rename operations in wide area file systems
US6895512B1 (en) Methods and systems for synchronizing security descriptors in systems that use multiple security descriptor specifications
US7359926B1 (en) System for optimization of database replication/synchronization
US7478115B2 (en) System and method for database and filesystem coordinated transactions
US7047234B2 (en) System and method for managing database access
CN116668470A (en) Remote multi-main storage method and device based on conflict-free copy data type
Lee et al. A distributed backup agent based on grid computing architecture
CN113051108A (en) Data backup method and system

Legal Events

Date Code Title Description
AS Assignment

Owner name: STAMPEDE TECHNOLOGIES, INC., OHIO

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:YOHE, THOMAS P.;MORRIS, BRIAN C.;REEL/FRAME:013780/0032;SIGNING DATES FROM 20030212 TO 20030214

STCF Information on status: patent grant

Free format text: PATENTED CASE

AS Assignment

Owner name: COMTECH EF DATA CORPORATION, ARIZONA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:STAMPEDE TECHNOLOGIES, INC.;REEL/FRAME:025105/0546

Effective date: 20100930

FEPP Fee payment procedure

Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

FEPP Fee payment procedure

Free format text: PAT HOLDER NO LONGER CLAIMS SMALL ENTITY STATUS, ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: STOL); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

FPAY Fee payment

Year of fee payment: 4

FPAY Fee payment

Year of fee payment: 8

AS Assignment

Owner name: CITIBANK N.A., AS ADMINISTRATIVE AGENT, NEW YORK

Free format text: SECURITY AGREEMENT;ASSIGNORS:COMTECH EF DATA CORP.;COMTECH XICOM TECHNOLOGY, INC.;COMTECH MOBILE DATACOM CORPORATION;AND OTHERS;REEL/FRAME:037993/0001

Effective date: 20160223

FEPP Fee payment procedure

Free format text: 11.5 YR SURCHARGE- LATE PMT W/IN 6 MO, LARGE ENTITY (ORIGINAL EVENT CODE: M1556); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 12TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1553); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 12