International Business Machines Corporation

Claire Willey McFeely

Tammie Dang

Curt Lee Cotner

Maryela Evelin Weihrauch

Yao-Ching Stephen Chen

Fen-Ling Lin

James Willis Pickel

Jay A Yothers

Fung Lee

Xiaohong Fu

Binghui Zhong

Margaret Ann Bernal

Yumi Kimura Tsuji

Margaret Zagelow

David J Kuang

Illong A Huang

Hui-An Lee

Baoqiu Cui

Joe Cheng-yu Huang

Gerald George Kiernan

Julie Ann Watts

Walid Rjaibi

Kalpana Shyam

Timothy Jon Vincent

John Joseph Campbell

William Robert Bireley

Christopher John Crone

Brian Keith Howell

Shengxi Suo

Irene Ching-Hua Liu

Manogari Nogi Simanjuntak

Charles H Lin

Chunfeng Pei

Stephen Yao Ching Chen

Georgia Carroll Fuller

Ding-Wei Chieh

Koichi Yamaguchi

Liyan Zhou

Euna Park

Thomas Eng

Robert Thomas Miller

Jennifer W Ou

Marion B Farber

Xiaoyu Yang

Aspects of the invention include techniques for providing a schema evolution on a live database system without an outage. A non-limiting example method includes initiating a schema change on a live database system. The schema change includes an attribute for a database object. A first application package having a user application that is dependent on the database object and that is bound with a release(deallocate) option is identified. Existing threads and new threads executing the first application package are routed to execute the first application package with a release(commit) option and the schema change on the live database system is completed. One or more additional threads concurrently executing one or more additional application packages remain executing with the release(deallocate) option.

Schema evolution on a live database system without an outage

In managing multiple versions of triggers, a database system creates a first version of a trigger to apply a first set of actions in response to a first triggering event. The database system also creates a second version of the trigger to apply a second set of actions to the database object in response to a second triggering event. Upon receiving a command to set the current version of the trigger to the second version, the database system sets the second version as the current version of the trigger. When the triggering event of the trigger occurs, the database system determines that the second version is the current version of the trigger, retrieves the second set of actions in the second version, and executes the second set of actions.

Multiple versions of triggers in a database system

In supporting temporal logical transactions, a database management system (DBMS) determines that a temporal logical transaction time (T) is set for a temporal logical transaction. The DBMS receives a change request for a current row in a current table. A history row for a history table corresponding to the current table is created. The values in the history row are set to the values in the current row, where a begin time in the history row has same value as a begin time in the current row, and an end time in the history row is set to T. When the begin time equals the end time in the history row, the DBMS does not store the history row in the history table. The values in the current row are changed according to the change request, and the begin time in the current row is set to T.

Temporal logical transactions

In managing multiple versions of triggers, a database system creates a first version of a trigger to apply a first set of actions in response to a first triggering event, which includes: creating a first package for the first version of the trigger to include the first set of actions; linking the first package to the database object; and setting the first package as a current version of the trigger. The database system creates a second version of the trigger to apply a second set of actions to the database object in response to a second triggering event, which includes: creating a second package for the second version of the trigger to include the second set of actions; and linking the second package to the database object. In response to a command, the database system sets the current version of the trigger to the second package.

Access to a data element stored within a database object is controlled. A request is received from a user to perform an operation in relation to the database object, the operation including retrieval of information from the data element of the database object. Prior to retrieving information from the data element, a determination is made whether at least a portion of the information from the data element is subject to masking in accordance with an access policy. In response to determining that information from the data element is subject to masking, the request is modified to require that information from the data element be retrieved in a masked condition.

Masking sensitive data of table columns retrieved from a database

A method and system for providing package resolution in a database system is disclosed. The method and system comprise providing a statement within a server which allows an application to identify a list of package collections. The method and system further includes executing the statement to obtain the appropriate package. A system and method in accordance with the present invention provides a new current package path value, which is set via a statement referred to as Set Current Package Path. The SET CURRENT PACKAGE PATH statement allows the application to supply a precedence list of qualified package collections during execution time, therefore the scheme for resolving packages can be changed at any point during execution. The SET CURRENT PACKAGE PATH statement improves application development by making the package resolution mechanism less error prone and less tedious for the application developer, while providing an optimal-performance solution in the client-server environment.

Package resolution mechanism for database systems

An SQL procedure deployment system deploys a query procedure comprising a procedural logic component and a database request component from a source system to a target system. At generation of the query procedure, the system generates a query procedure source code, a symbol table, and an encapsulated optimization results to regenerate run-time instructions for query statements of the database request component and make the query statements function with a deployed procedural logic component. The system maintains an association between the procedural logic component and the database request component during deployment. The system copies an internal representation of the procedural logic component to the target system without regeneration. The system regenerates the database request component to recreate the query procedure on the target system and to maintain a consistent interface between the procedural logic component and database request component.

System and method for deploying an SQL procedure

Techniques are provided for supporting versions of a routine. A first version of the routine is created. A second version of the routine is generated in response to receiving an alter statement including an add version clause. The second version of the routine is activated in response to receiving an alter statement including an activate version clause.

Supporting multiple versions of a routine

Provided are a method, system, and program for making data available to an application program. A cursor is generated positioned with respect to a result table, wherein the cursor specifies a search criteria, and wherein the result table includes rows from a base table that satisfy the search criteria. A fetch request is received indicating to position the cursor on a plurality of rows of the result table. The cursor is positioned on the plurality of rows of the result table indicated in the fetch request that satisfy the search criteria.

Method, system, and program for positioning a cursor on rows of a result table

Aspects for dynamically changing attributes in an embedded-SQL application are described. In these aspects, an option is provided within a standard SQL statement for specifying one or more attributes of at least a declared cursor. The standard SQL statement is then processed to include the specified one or more attributes in at least the declared cursor. The provision occurs with an ATTRIBUTES option and within a PREPARE SQL statement.

Method and system for dynamically changing cursor attributes in an embedded SQL application

Growing community of inventors

San Jose, CA, United States of America

Claire Willey McFeely