会员体验
专利管家(专利管理)
工作空间(专利管理)
风险监控(情报监控)
数据分析(专利分析)
侵权分析(诉讼无效)
联系我们
交流群
官方交流:
QQ群: 891211   
微信请扫码    >>>
现在联系顾问~
热词
    • 4. 发明授权
    • Optimization of SQL queries using early-out join transformations of
column-bound relational tables
    • 使用列关联表的早期连接变换优化SQL查询
    • US5548758A
    • 1996-08-20
    • US463968
    • 1995-06-05
    • Mir H. PiraheshTing Y. LeungGuy M. LohmanEugene J. ShekitaDavid E. Simmen
    • Mir H. PiraheshTing Y. LeungGuy M. LohmanEugene J. ShekitaDavid E. Simmen
    • G06F17/30
    • G06F17/30454Y10S707/99932Y10S707/99935
    • A method and apparatus for optimizing SQL queries in a relational database management system uses early-out join transformations. An early-out join comprises a many-to-one existential join, wherein the join scans an inner table for a match for each row of the outer table and terminates the scan for each row of the outer table when a single match is found in the inner table. To transform a many-to-many join to an early-out join, the query must include a requirement for distinctiveness, either explicitly or implicitly, in one or more result columns for the join operation. Distinctiveness can be specified using the DISTINCT keyword in the SELECT clause or can be implied from the predicates present in the query. The early-out join transformation also requires that no columns of the inner table be referenced after the join, or if an inner table column is referenced after the join, that each referenced column be "bound". A referenced column can be bound in one of three ways: (1) an inner table column can be bound to a constant through an equality predicate, (2) an inner table column can be bound to an outer table column, or (3) an inner table column can be bound to a correlated value, wherein the correlated value originates outside the query block. In all three cases, an inner table column can be bound through the transitivity of equality predicates.
    • 用于优化关系数据库管理系统中的SQL查询的方法和装置使用早期连接变换。 早期连接包括多对一存在连接,其中,连接扫描内部表以获取外部表的每一行的匹配,并且当找到单个匹配时终止外部表的每一行的扫描 内表。 要将多对多连接转换为早期连接,查询必须在连接操作的一个或多个结果列中明确或隐式地包含独特性的要求。 可以使用SELECT子句中的DISTINCT关键字指定不同之处,也可以从查询中存在的谓词中暗示。 早期连接转换还要求在连接之后不引用内部列的列,或者如果在连接之后引用了内部列列,则每个引用的列都将被“绑定”。 引用的列可以通过三种方式之一来绑定:(1)内表列可以通过相等谓词绑定到常量,(2)内表列可绑定到外表列,或(3) 可以将内表列绑定到相关值,其中相关值起始于查询块之外。 在所有三种情况下,内表列可以通过相等谓词的传递性来约束。
    • 5. 发明授权
    • Optimization of SQL queries using early-out join transformations
    • 使用Early-out连接变换优化SQL查询
    • US5548754A
    • 1996-08-20
    • US385177
    • 1995-02-07
    • Mir H. PiraheshTing Y. LeungGuy M. LohmanEugene J. ShekitaDavid E. Simmen
    • Mir H. PiraheshTing Y. LeungGuy M. LohmanEugene J. ShekitaDavid E. Simmen
    • G06F17/30
    • G06F17/30454Y10S707/99932Y10S707/99935
    • A method and apparatus for optimizing SQL queries in a relational database management system uses early-out join transformations. An early-out join comprises a many-to-one existential join, wherein the join scans an inner table for a match for each row of the outer table and terminates the scan for each row of the outer table when a single match is found in the inner table. To transform a many-to-many join to an early-out join, the query must include a requirement for distinctiveness, either explicitly or implicitly, in one or more result columns for the join operation. Distinctiveness can be specified using the DISTINCT keyword in the SELECT clause or can be implied from the predicates present in the query. The early-out join transformation also requires that no columns of the inner table be referenced after the join, or if an inner table column is referenced after the join, that each referenced column be "bound". A referenced column can be bound in one of three ways: (1) an inner table column can be bound to a constant through an equality predicate, (2) an inner table column can be bound to an outer table column, or (3) an inner table column can be bound to a correlated value, wherein the correlated value originates outside the query block. In all three cases, an inner table column can be bound through the transitivity of equality predicates.
    • 用于优化关系数据库管理系统中的SQL查询的方法和装置使用早期连接变换。 早期连接包括多对一存在连接,其中,连接扫描内部表以获取外部表的每一行的匹配,并且当找到单个匹配时终止外部表的每一行的扫描 内表。 要将多对多连接转换为早期连接,查询必须在连接操作的一个或多个结果列中明确或隐式地包含独特性的要求。 可以使用SELECT子句中的DISTINCT关键字指定不同之处,也可以从查询中存在的谓词中暗示。 早期连接转换还要求在连接之后不引用内部列的列,或者如果在连接之后引用了内部列列,则每个引用的列都将被“绑定”。 引用的列可以通过三种方式之一来绑定:(1)内表列可以通过相等谓词绑定到常量,(2)内表列可绑定到外表列,或(3) 可以将内表列绑定到相关值,其中相关值起始于查询块之外。 在所有三种情况下,内表列可以通过相等谓词的传递性来约束。
    • 6. 发明授权
    • Multiple version database concurrency control system
    • 多版本数据库并发控制系统
    • US5280612A
    • 1994-01-18
    • US801769
    • 1991-11-26
    • Raymond A. LorieChandrasekaran MohanMir H. Pirahesh
    • Raymond A. LorieChandrasekaran MohanMir H. Pirahesh
    • G06F12/00G06F17/30G06F15/40
    • G06F17/30356G06F17/30362Y10S707/99938Y10S707/99939Y10S707/99953
    • An improved concurrency control system for application to a distributed concurrent transaction and query processing system using multi-version database records to overcome delays arising from lock conflicts. Read-only queries are afforded a consistent "stable state" of the database during the life of the query. Updating transactions requiring locks can proceed without waiting for the termination of long queries. At least two database versions are necessary, although availability of more versions permits long read-only queries to phase-out over time without forcing new queries to use aged "stable-state" data and without roll-back. Read-only queries can be terminated and converted to locking transactions to permit an update of the "stable state" database version before the queries would normally terminate. A novel record key structure having a plurality of substructures corresponding to the several database versions is used to access database records. Rapid selection of proper record version and efficient version tracking and updating is effected using several bit-mapped transaction index tables.
    • 一种改进的并发控制系统,用于应用于分布式并发事务和查询处理系统,使用多版本数据库记录来克服由锁定冲突引起的延迟。 在查询期间,只读查询提供了数据库一致的“稳定状态”。 更新需要锁定的事务可以进行,而无需等待长时间查询的终止。 至少需要两个数据库版本,尽管更多版本的可用性允许长时间只读查询逐渐淘汰,而不会强制新查询使用老化的“稳定状态”数据,而无需回滚。 只读查询可以终止并转换为锁定事务,以便在查询正常终止之前更新“稳定状态”数据库版本。 具有对应于多个数据库版本的多个子结构的新颖的记录关键结构被用于访问数据库记录。 使用几个位映射的事务索引表来快速选择适当的记录版本和高效的版本跟踪和更新。
    • 7. 发明授权
    • Program storage device and computer program product for outer join
operations using responsibility regions assigned to inner tables in a
relational database
    • 程序存储设备和外部连接操作的计算机程序产品,使用分配给关系数据库中的内部表的责任区域
    • US5551031A
    • 1996-08-27
    • US487300
    • 1995-06-07
    • Josephine M. ChengChandrasekaran MohanMir H. Pirahesh
    • Josephine M. ChengChandrasekaran MohanMir H. Pirahesh
    • G06F17/30
    • G06F17/30498Y10S707/99932
    • A computer database system utilizes a method for performing a right outer join of database tables without sorting the inner table (T.sub.2). The processing of each tuple in the outer table (T.sub.1) includes the preservation in the joint output of all tuples in T.sub.2 which are in its responsibility region. The initialization step of the process preserves in the join output all of the tuples in T.sub.2 which have column set values less than the lowest column set value in T.sub.1, i.e. the first tuple in T.sub.1, since T.sub.1 is sorted or accessed using a sorted index. The responsibility region for tuples in T.sub.1, other than the last tuple, is defined as those tuples which have column set values less than the column set value for the next tuple in T.sub.1 and greater than or equal to the column set value for the current T.sub.1 tuple. The last tuple in T.sub.1 must preserve all of the tuples in T.sub.2 which have not already been preserved in T.sub.2, i.e. all tuples greater than or equal to its column set value. If T.sub.1 has duplicate values for the column set value, only the last one preserves the associated T.sub.2 tuples. Additional methods for parallel execution of the outer join methods and methods for applying the outer join methods to subqueries (i.e., an All (or universal) Right Join (ARJOIN) and an Existential Right Join (ERJOIN)) are described.
    • 计算机数据库系统利用用于执行数据库表的右外连接的方法,而不排序内表(T2)。 外表(T1)中每个元组的处理包括在其责任区域的T2中所有元组的联合输出中的保存。 该进程的初始化步骤在连接输出中保留所有T2中的元组,它们的列设置值小于T1中的最低列设置值,即T1中的第一个元组,因为使用排序索引对T1进行排序或访问。 T1中的元组的责任区域除了最后一个元组之外,被定义为具有小于T1中下一个元组的列设置值的列设置值大于或等于当前T1的列设置值的元组 元组 T1中的最后一个元组必须保留T2中尚未保存在T2中的所有元组,即大于或等于其列设置值的所有元组。 如果T1具有列设置值的重复值,则只有最后一个值保留关联的T2元组。 描述了用于并行执行外连接方法和将外连接方法应用于子查询(即,全(或通用)右连接(ARJOIN)和存在右连接(ERJOIN))的附加方法。
    • 8. 发明授权
    • Outer join operations using responsibility regions assigned to inner
tables in a relational database
    • 使用分配给关系数据库中的内部表的责任区域进行外部连接操作
    • US5557791A
    • 1996-09-17
    • US325942
    • 1994-10-19
    • Josephine M. ChengChandrasekaran MohanMir H. Pirahesh
    • Josephine M. ChengChandrasekaran MohanMir H. Pirahesh
    • G06F17/30
    • G06F17/30498Y10S707/99932
    • A computer database system utilizes a method for performing a right outer join of database tables without sorting the inner table (T.sub.2). The processing of each tuple in the outer table (T.sub.1) includes the preservation in the joint output of all tuples in T.sub.2 which are in its responsibility region. The initialization step of the process preserves in the join output all of the tuples in T.sub.2 which have column set values less than the lowest column set value in T.sub.1, i.e. the first tuple in T.sub.1, since T.sub.1 is sorted or accessed using a sorted index. The responsibility region for tuples in T.sub.1, other than the last tuple, is defined as those tuples which have column set values less than the column set value for the next tuple in T.sub.1 and greater than or equal to the column set value for the current T.sub.1 tuple. The last tuple in T.sub.1 must preserve all of the tuples in T.sub.2 which have not already been preserved in T.sub.2, i.e. all tuples greater than or equal to its column set value. If T.sub.1 has duplicate values for the column set value, only the last one preserves the associated T.sub.2 tuples. Additional methods for parallel execution of the outer join methods and methods for applying the outer join methods to subqueries (i.e., an All (or universal) Right Join (ARJOIN) and an Existential Right Join (ERJOIN)) are described.
    • 计算机数据库系统利用用于执行数据库表的右外连接的方法,而不排序内表(T2)。 外表(T1)中每个元组的处理包括在其责任区域的T2中所有元组的联合输出中的保存。 该进程的初始化步骤在连接输出中保留所有T2中的元组,它们的列设置值小于T1中的最低列设置值,即T1中的第一个元组,因为使用排序索引对T1进行排序或访问。 T1中的元组的责任区域除了最后一个元组之外,被定义为具有小于T1中下一个元组的列设置值的列设置值大于或等于当前T1的列设置值的元组 元组 T1中的最后一个元组必须保留T2中尚未保存在T2中的所有元组,即大于或等于其列设置值的所有元组。 如果T1具有列设置值的重复值,则只有最后一个值保留关联的T2元组。 描述了用于并行执行外连接方法和将外连接方法应用于子查询(即,全(或通用)右连接(ARJOIN)和存在右连接(ERJOIN))的附加方法。
    • 9. 发明授权
    • Evaluation strategy for execution of SQL queries involving recursion and
table queues
    • 执行涉及递归和表队列的SQL查询的评估策略
    • US5546570A
    • 1996-08-13
    • US390112
    • 1995-02-17
    • John A. McPherson, Jr.Mir H. PiraheshTuong C. TruongDaniel J. Coyle, Jr.
    • John A. McPherson, Jr.Mir H. PiraheshTuong C. TruongDaniel J. Coyle, Jr.
    • G06F17/30
    • G06F17/30595Y10S707/954Y10S707/99932Y10S707/99934
    • The present invention provides an evaluation strategy for the execution of SQL queries involving recursion and table queues in a relational database management system. The table queue is established for the query in the memory of the computer, and tuples are generated by tuple-producing operators in the query for storage into the table queue. As operators of the query read the stored tuples from the table queue, a first end-of-file condition, termed a Temporary End-Of-File, occurs when all of the tuples currently stored in the table queue have been retrieved and control is returned to the operator reading from the table queue. A retry request for additional tuples is generated by the operator through the table queue to the tuple-producing operators. If the tuple-producing operators can generate additional tuples, then these additional tuples are stored into the table queue and control is returned to the operator reading from the table queue in response to the retry request. If the tuple-producing operators cannot generate the additional tuples, then a second end-of-file condition, termed a Permanent End-Of-File, occurs and control is returned to the operator reading from the table queue.
    • 本发明提供了在关系数据库管理系统中执行涉及递归和表队列的SQL查询的评估策略。 为计算机的存储器中的查询建立表队列,并且元组由查询中的元组生成操作符生成,用于存储到表队列中。 当查询的运算符从表队列中读取存储的元组时,当检索到当前存储在表队列中的所有元组,并且控件为“否”时,会发生称为临时文件结束文件的第一个文件结束条件 返回到操作员从表队列中读取。 对于额外的元组的重试请求由操作员通过表队列生成到元组生成操作符。 如果元组生成操作符可以生成额外的元组,那么这些额外的元组被存储到表队列中,并且响应于重试请求将控制返回给操作员从表队列读取。 如果元组生成运算符不能生成额外的元组,则会发生称为永久文件结束的第二个文件结束条件,并将控制权从表队列返回给操作员进行读取。
    • 10. 发明授权
    • Query optimizer system that detects and prevents mutating table
violations of database integrity in a query before execution plan
generation
    • 在执行计划生成之前,查询优化器系统检测和防止在查询中突变表违反数据库完整性
    • US5546576A
    • 1996-08-13
    • US390196
    • 1995-02-17
    • Roberta J. CochraneMir H. PiraheshRichard S. Sidle
    • Roberta J. CochraneMir H. PiraheshRichard S. Sidle
    • G06F17/30
    • G06F17/30448G06F17/30371G06F17/3051Y10S707/99932
    • An automated system for detecting and preventing mutating table violations of database integrity in a SQL query before generation and selection of an optimal query execution plan (QEP). This system modifies the query graph model (QGM) to restrict the choice of execution plans to those that avoid mutating table integrity (MTI) violations, thereby forcing database integrity during table mutation when executing the optimal QEP. Mutating table integrity violations are detected by evaluating the position in the QGM of each write-node referencing a particular base table with respect to each of the positions of all other read- and write-nodes referencing of the same base table. Every common-referencing node pair is tested for sequencing conflicts and a data-flow dam is inserted in the QGM where necessary to force the completion of the execution of one node before initiating execution of the other common-referencing node. The system of this invention allows processing of all non-cyclic and most cyclic SQL queries known to cause mutating table integrity violations, such as queries having searched and positioned inserts, deletes and updates, and row-level triggers.
    • 一种用于在生成和选择最优查询执行计划(QEP)之前,在SQL查询中检测和防止突变表违反数据库完整性的自动化系统。 该系统修改查询图模型(QGM),将执行计划的选择限制为避免突变表完整性(MTI)违规的选择,从而在执行最佳QEP时强制表突变期间的数据库完整性。 通过评估参考相同基准表的所有其他读 - 写节点的每个位置的引用特定基表的每个写节点的QGM中的位置来检测突变表完整性违反。 测试每个共同参考节点对的排序冲突,并且在QGM中插入数据流大坝,必要时强制完成一个节点的执行,然后再启动其他公共引用节点的执行。 本发明的系统允许处理已知导致突变表完整性违例的所有非循环和大多数循环SQL查询,例如具有搜索和定位的插入,删除和更新的查询以及行级触发器。