会员体验
专利管家(专利管理)
工作空间(专利管理)
风险监控(情报监控)
数据分析(专利分析)
侵权分析(诉讼无效)
联系我们
交流群
官方交流:
QQ群: 891211   
微信请扫码    >>>
现在联系顾问~
热词
    • 1. 发明授权
    • Data change ordering in multi-log based replication
    • 基于多日志的复制中的数据更改排序
    • US08078582B2
    • 2011-12-13
    • US12418635
    • 2009-04-06
    • Rui WangPeter ByrneLeigh M. StewartRobin D. DhamankarQun GuoMichael E. HabbenXiaowei Jiang
    • Rui WangPeter ByrneLeigh M. StewartRobin D. DhamankarQun GuoMichael E. HabbenXiaowei Jiang
    • G06F17/30
    • G06F17/30368
    • Aspects of the subject matter described herein relate to data change ordering in multi-log based replication. In aspects, local seeds are maintained for subtransactions involved in a transaction, where each subtransaction may occur on a different node that hosts one or more database fragments involved in the transaction. When a subtransaction communicates with another subtransaction in a transaction, the subtransaction sends its local seed to the other subtransaction. The receiving subtransaction compares its local seed with the received seed and updates its local seed if the received seed is logically after its local seed. A subtransaction uses a local seed to generate sequence identifiers for changes made by the subtransaction. These identifiers allow data changes of a transaction that are made on multiple nodes to be partially ordered relative to other changes made during the transaction.
    • 本文描述的主题的方面涉及基于多日志的复制中的数据改变排序。 在方面中,维护涉及事务的子事务的局部种子,其中每个子事务可以在承载事务涉及的一个或多个数据库片段的不同节点上发生。 当子事务与事务中的另一个子事务通信时,子事务将其本地种子发送到另一个子事务。 接收的子事务将其本地种子与接收的种子进行比较,如果接收的种子在其本地种子之后是逻辑上的,则更新其本地种子。 子事务使用本地种子为子事务所做的更改生成序列标识符。 这些标识符允许在多个节点上进行的事务的数据更改相对于在事务期间进行的其他更改而被部分排序。
    • 2. 发明申请
    • DATA CHANGE ORDERING IN MULTI-LOG BASED REPLICATION
    • 数据更改在多种方式下进行更新
    • US20100257138A1
    • 2010-10-07
    • US12418635
    • 2009-04-06
    • Rui WangPeter ByrneLeigh M. StewartRobin D. DhamankarQun GuoMichael E. HabbenXiaowei Jiang
    • Rui WangPeter ByrneLeigh M. StewartRobin D. DhamankarQun GuoMichael E. HabbenXiaowei Jiang
    • G06F17/30
    • G06F17/30368
    • Aspects of the subject matter described herein relate to data change ordering in multi-log based replication. In aspects, local seeds are maintained for subtransactions involved in a transaction, where each subtransaction may occur on a different node that hosts one or more database fragments involved in the transaction. When a subtransaction communicates with another subtransaction in a transaction, the subtransaction sends its local seed to the other subtransaction. The receiving subtransaction compares its local seed with the received seed and updates its local seed if the received seed is logically after its local seed. A subtransaction uses a local seed to generate sequence identifiers for changes made by the subtransaction. These identifiers allow data changes of a transaction that are made on multiple nodes to be partially ordered relative to other changes made during the transaction.
    • 本文描述的主题的方面涉及基于多日志的复制中的数据改变排序。 在方面中,维护涉及事务的子事务的局部种子,其中每个子事务可以在承载事务涉及的一个或多个数据库片段的不同节点上发生。 当子事务与事务中的另一个子事务通信时,子事务将其本地种子发送到另一个子事务。 接收的子事务将其本地种子与接收的种子进行比较,如果接收的种子在其本地种子之后是逻辑上的,则更新其本地种子。 子事务使用本地种子为子事务所做的更改生成序列标识符。 这些标识符允许在多个节点上进行的事务的数据更改相对于在事务期间进行的其他更改而被部分排序。
    • 5. 发明申请
    • DE-DUPLICATION AND COMPLETENESS IN MULTI-LOG BASED REPLICATION
    • 多重复制的复制和完整性
    • US20100274768A1
    • 2010-10-28
    • US12428495
    • 2009-04-23
    • Rui WangQun GuoYixue ZhuMichael E. Habben
    • Rui WangQun GuoYixue ZhuMichael E. Habben
    • G06F7/00G06F12/08G06F12/00
    • G06F17/30575G06F17/30368
    • Aspects of the subject matter described herein relate to multi-log based replication. In aspects, database fragments are associated with different logs. Each change to a duplicated database record may be recorded in multiple logs. A history data structure is used to determine when duplication schemas are valid. A duplication schema indicates what database fragments duplicate one or more database records. For a particular time range, the duplication schema history is used to determine whether currently available logs include all changes. If multiple logs include the same change, one log may be selected to provide the change. Non-duplicative changes may be placed into a single data stream usable to update a remote database.
    • 本文描述的主题的方面涉及基于多日志的复制。 在方面,数据库碎片与不同的日志相关联。 对重复数据库记录的每次更改可能会记录在多个日志中。 历史数据结构用于确定重复模式何时有效。 复制模式指示什么数据库片段复制一个或多个数据库记录。 对于特定时间范围,复制模式历史记录用于确定当前可用日志是否包括所有更改。 如果多个日志包含相同的更改,则可以选择一个日志来提供更改。 可以将不重复的更改放置在可用于更新远程数据库的单个数据流中。
    • 7. 发明授权
    • De-duplication and completeness in multi-log based replication
    • 基于多日志的复制中的重复数据删除和完整性
    • US08108343B2
    • 2012-01-31
    • US12428495
    • 2009-04-23
    • Rui WangQun GuoYixue ZhuMichael E. Habben
    • Rui WangQun GuoYixue ZhuMichael E. Habben
    • G06F7/00G06F17/00
    • G06F17/30575G06F17/30368
    • Aspects of the subject matter described herein relate to multi-log based replication. In aspects, database fragments are associated with different logs. Each change to a duplicated database record may be recorded in multiple logs. A history data structure is used to determine when duplication schemas are valid. A duplication schema indicates what database fragments duplicate one or more database records. For a particular time range, the duplication schema history is used to determine whether currently available logs include all changes. If multiple logs include the same change, one log may be selected to provide the change. Non-duplicative changes may be placed into a single data stream usable to update a remote database.
    • 本文描述的主题的方面涉及基于多日志的复制。 在方面,数据库碎片与不同的日志相关联。 对重复数据库记录的每次更改可能会记录在多个日志中。 历史数据结构用于确定重复模式何时有效。 复制模式指示什么数据库片段复制一个或多个数据库记录。 对于特定时间范围,复制模式历史记录用于确定当前可用日志是否包括所有更改。 如果多个日志包含相同的更改,则可以选择一个日志来提供更改。 可以将不重复的更改放置在可用于更新远程数据库的单个数据流中。
    • 8. 发明授权
    • System and method of distributing replication commands
    • 分发复制命令的系统和方法
    • US07707181B2
    • 2010-04-27
    • US10370389
    • 2003-02-19
    • Qun GuoMichael E. Habben
    • Qun GuoMichael E. Habben
    • G06F17/30
    • G06F17/30575
    • A transactional replication system wherein each replicated command applies to a single row as identified by the primary key, replicated commands are dispatched among multiple connections by hashing of primary key from a single command queue to ensure that changes to the same data row are always dispatched to the same connection to maintain the order of commands as originally occurred on publisher. All connections commit their transactions at the same time in a coordinated fashion without a two phase commit. Retry logic based on a logical sequence number is used to reapply commands from any connection that fails to commit.
    • 一种事务复制系统,其中每个复制命令适用于由主键标识的单个行,通过从单个命令队列中的主键散列来确保对相同数据行的更改始终被分派到多个连接中,复制命令 相同的连接来保持最初发生在发布者上的命令顺序。 所有连接以协调的方式同时提交其事务,而不进行两阶段提交。 基于逻辑序列号的重试逻辑用于重新应用任何无法提交的连接的命令。
    • 9. 发明授权
    • System for generating a gapless series of identity values
    • 用于产生无缝系列身份值的系统
    • US5862318A
    • 1999-01-19
    • US548677
    • 1995-10-26
    • Michael E. Habben
    • Michael E. Habben
    • G06F11/14G06F11/34G06F17/30
    • G06F17/30368G06F11/1471G06F17/30289Y10S707/99953
    • A system for generating a gapless series of identity values in a history log maintained in a database by a database management system without adversely impacting database performance. The system comprises the steps of determining a last used identity value independent of an intervening disruptive event that is disruptive to the database management system, generating a next identity value based on the last used identity value, and inserting a record of an event into the history log wherein a change record event contains the next identity value. Determining the last used identity value in the history log depending on whether or not a disruptive event has occurred during normal transaction processing. Absent a disruptive event, the last used identity value is the identity value used in the most recent change record insertion. In the event of a disruptive event, the last used identity value is retrieved from the last change record of the last committed transaction in the history log as the database recovery phase traverses the history log to identify committed transactions for reapplication and incomplete transactions for rollback to bring the database to a consistent state.
    • 一种用于通过数据库管理系统在数据库中维护的历史日志中生成无间隙的一系列身份值的系统,而不会对数据库性能造成不利影响。 该系统包括以下步骤:确定最后使用的身份值,独立于对数据库管理系统具有破坏性的干扰中断事件,基于最后使用的身份值生成下一个身份值,并将事件的记录插入到历史记录中 日志,其中改变记录事件包含下一个标识值。 根据在正常事务处理期间是否发生中断事件,确定历史记录日志中的最后使用的标识值。 没有中断事件,最后使用的身份值是最近更改记录插入中使用的身份值。 在发生中断事件的情况下,最后一次使用的身份值将从历史记录日志中最后一个提交的事务的最后一个更改记录中检索,因为数据库恢复阶段遍历历史记录日志,以识别重新应用的重新应用和不完整的事务以便回滚到 使数据库保持一致状态。