会员体验
专利管家(专利管理)
工作空间(专利管理)
风险监控(情报监控)
数据分析(专利分析)
侵权分析(诉讼无效)
联系我们
交流群
官方交流:
QQ群: 891211   
微信请扫码    >>>
现在联系顾问~
热词
    • 71. 发明申请
    • STRUCTURE OF HIERARCHICAL COMPRESSED DATA STRUCTURE FOR TABULAR DATA
    • 用于数据数据的分层压缩数据结构的结构
    • US20100278446A1
    • 2010-11-04
    • US12617669
    • 2009-11-12
    • Amit GaneshVikram KapoorVineet MarwahKam ShergillRoger MacNicolSachin KulkarniJesse Kamp
    • Amit GaneshVikram KapoorVineet MarwahKam ShergillRoger MacNicolSachin KulkarniJesse Kamp
    • G06K9/36
    • G06F17/30315
    • A highly flexible and extensible structure is provided for physically storing tabular data. The structure, is referred to as a compression unit, and may be used to physically store tabular data that logically resides in any type of table-like structure. According to one embodiment, compression units are recursive. Thus, a compression unit may have a “parent” compression unit to which it belongs, and may have one or more “child” compression units that belong to it. In one embodiment, compression units include metadata that indicates how the tabular data is stored within them. The metadata for a compression unit may indicate, for example, whether the data within the compression unit is stored in row-major or column major-format (or some combination thereof), the order of the columns within the compression unit (which may differ from the logical order of the columns dictated by the definition of their logical container), a compression technique for the compression unit, the child compression units (if any), etc.
    • 提供了高度灵活和可扩展的结构,用于物理存储表格数据。 该结构被称为压缩单元,并且可以用于物理地存储逻辑上驻留在任何类型的表状结构中的表格数据。 根据一个实施例,压缩单元是递归的。 因此,压缩单元可以具有它所属的“父”压缩单元,并且可以具有属于它的一个或多个“子”压缩单元。 在一个实施例中,压缩单元包括指示表格数据如何被存储在其中的元数据。 压缩单元的元数据例如可以指示压缩单元内的数据是以主要或列主格式(或其某种组合)存储的,压缩单元中的列的顺序(其可以不同 从逻辑容器的定义指定的列的逻辑顺序),压缩单元的压缩技术,子压缩单元(如果有的话)等等
    • 73. 发明申请
    • CASCADING INDEX COMPRESSION
    • US20090292947A1
    • 2009-11-26
    • US12469637
    • 2009-05-20
    • Amit GaneshJuan R. LoaizaKrishna Kunchithapadam
    • Amit GaneshJuan R. LoaizaKrishna Kunchithapadam
    • G06F11/07G06F17/30
    • G06F11/1474G06F17/30
    • Techniques for maintaining a cascading index are provided. In one approach, one or more branch node compression techniques are applied to the main index of a cascading index. In an approach, a Bloom filter is generated and associated with, e.g., a branch node in the main index. The Bloom filter is used to determine whether, without accessing any leaf blocks, a particular key value exists, e.g., in leaf blocks associated with the branch node. In an approach, a new redo record is generated in response to a merge operation between two levels of the cascading index. The new redo record comprises (a) one or more addresses of blocks that are affected by the merge operation, (b) data is that being “pushed down” to a lower level of the cascading index, and (c) one or more addresses of blocks that are written to disk storage as a result of the merge operation.
    • 提供了维护级联索引的技术。 在一种方法中,一个或多个分支节点压缩技术被应用于级联索引的主索引。 在一种方法中,生成Bloom过滤器并与例如主索引中的分支节点相关联。 Bloom过滤器用于确定在不访问任何叶片块的情况下是否存在特定的键值,例如在与分支节点相关联的叶片块中。 在一种方法中,响应于级联索引的两个级别之间的合并操作,生成新的重做记录。 新的重做记录包括(a)受合并操作影响的块的一个或多个地址,(b)数据被“下推”到级联索引的较低级,以及(c)一个或多个地址 作为合并操作的结果写入磁盘存储的块。
    • 75. 发明申请
    • Framework to optimize delete all rows operations on database objects
    • 优化框架来删除数据库对象上的所有行操作
    • US20070288529A1
    • 2007-12-13
    • US11450092
    • 2006-06-09
    • Amit GaneshNiloy MukherjeeManosiz BhattacharyyaBipul Sinha
    • Amit GaneshNiloy MukherjeeManosiz BhattacharyyaBipul Sinha
    • G06F17/30
    • G06F17/30442
    • A bulk delete operation with reduced latency allows for retrieval of deleted data. Each database object holds a Delete SCN indicating when a bulk delete operation was last performed. Each row in the database object holds a Row Modification SCN indicating when the row was last updated. A bulk delete is performed by writing the old value of the Delete SCN to the undo tablespace and updating the Delete SCN. No undo information is stored for the rows. A write is performed by finding a deleted row, storing undo information for the deleted row and writing over the deleted row. To read from the database object, a rollback operation is performed, if necessary. Those rows are then retrieved for which the Row Modification SCN is higher than the Delete SCN and is less than or equal to the timestamp for the requested data.
    • 减少延迟的批量删除操作允许检索已删除的数据。 每个数据库对象保存一个删除SCN,指示上次执行批量删除操作的时间。 数据库对象中的每一行都保存一行行修改SCN,指示行何时上次更新。 通过将删除SCN的旧值写入undo表空间并更新删除SCN来执行批量删除。 没有为行存储撤消信息。 通过查找删除的行,存储删除的行的撤消信息并写入被删除的行来执行写入。 要从数据库对象读取,必要时执行回滚操作。 然后检索行修改SCN高于删除SCN并且小于或等于所请求数据的时间戳的那些行。
    • 76. 发明申请
    • Database-driven distributed recovery
    • 数据库驱动的分布式恢复
    • US20060149791A1
    • 2006-07-06
    • US11031275
    • 2005-01-06
    • Bipul SinhaAmit GaneshVivekanandhan Raja
    • Bipul SinhaAmit GaneshVivekanandhan Raja
    • G06F17/30
    • G06F9/466G06F16/2365
    • A method and apparatus for database-driven distributed recovery is provided. According to one aspect, a transaction manager sends, to one or more resource managers, connection information that indicates how to connect to the transaction manager. A resource manager that receives the connection information establishes an association between the connection information and the distributed transaction for which the connection information was received. If the resource manager is ever in doubt concerning whether the distributed transaction should be committed, the resource manager uses the associated connection information to send, to the transaction manager, a request for status information. The transaction manager maintains status information that indicates whether the distributed transaction should be committed, and responds to the resource manager with the requested status information. The resource manager receives the status information and, based on the status information, either commits or rolls back its portion of the distributed transaction.
    • 提供了一种用于数据库驱动的分布式恢复的方法和装置。 根据一个方面,事务管理器向一个或多个资源管理器发送指示如何连接到事务管理器的连接信息。 接收连接信息的资源管理器建立连接信息和接收到连接信息的分布式事务之间的关联。 如果资源管理器对于是否应该提交分布式事务是有疑问的,则资源管理器使用关联的连接信息向事务管理器发送状态信息请求。 事务管理器维护状态信息,指示是否应该提交分布式事务,并使用所请求的状态信息来响应资源管理器。 资源管理器接收状态信息,并根据状态信息提交或回滚其分布式事务的部分。