International Business Machines Corporation

Tammie Dang

Claire Willey McFeely

Curt Lee Cotner

James Willis Pickel

Fen-Ling Lin

William Robert Bireley

Maryela Evelin Weihrauch

Yao-Ching Stephen Chen

Jay A Yothers

Georgia Carroll Fuller

Paul Miller Bird

Bryan Frederick Smith

Hong Sang Tie

Margaret Ann Dong

Yumi Kimura Tsuji

Margaret Zagelow

Binghui Zhong

Kathryn Ruth Zeidenstein

David J Kuang

Euna Park

Michelle D Lam

Frankie K Sun

Hui-An Lee

Baoqiu Cui

Joe Cheng-yu Huang

Illong A Huang

Yun Yu Wang

James Z Teng

Donald J Haderle

Patrick Dooling Bossman

Kalpana Shyam

Akira Shibamiya

John Joseph Campbell

Paramesh Sampatrai Desai

Brian Keith Howell

Yao Ching Stephen Chen

Karelle Lynne Cornwell

Xiaohong Fu

Randy Mitchell Nakagawa

Shengxi Suo

Manogari Nogi Simanjuntak

Margaret Ann Bernal

Charles H Lin

Chunfeng Pei

Frank Darl Bower

Fung Lee

Jerome Quan Wong

Annie S Tsang

Ted Eric Blank

Koichi Yamaguchi

Ding-Wei Chieh

Liyan Zhou

Kouhorng Allen Yang

Thomas Eng

Robert Thomas Miller

Maureen Mae McDevitt

Beth Rivenes Moore

Kou Horng Yang

Peter Kuang

Darren Benjamin Swank

Frank Chan

Jennifer W Ou

Marion B Farber

Xiaoyu Yang

Dino Carlo Tonelli

Craig Leonard Sutton

Baoqui Cui

Yumi Kimara Tsuji

Joe Cheung-Yu c/oIBM Uk Ltd Ip Law Huang

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

A database system searches for any statements that satisfy one or more of a set of filtering criteria. When a given dynamic query statement fully satisfies the set of filtering criteria, the given statement is stabilized by persistently storing a bound form of the given dynamic query statement. When the given dynamic query statement partly satisfies the set of filtering criteria, a monitoring request is created with the set of filtering criteria to begin monitoring subsequent executions of the statement, and the statement is linked to the monitoring request. When the given dynamic query statement subsequently fully satisfies the set of filtering criteria, the statement is stabilized by persistently storing the bound form of the statement. When the given dynamic query is re-executed, the stabilized statement is loaded, and the PREPARE process is bypassed.

Method to monitor dynamic SQL statements for automatic stabilization in a data sharing environment

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.

An approach for using multiple plans in a database management system to access current data and history data is provided. The approach provides a first access plan for a query, stores the first plan as a first section in an application package. The first access plan is capable of accessing the current data. The approach determines whether a bind option for the query is detected. In response to determining that the bind option is detected, the approach provides a second access plan for the query and stores the second access plan as a second section in the application package. The second access plan is capable of accessing the current data and the history data.

Method for using multiple plans to achieve temporal and archive transparency performance

In a system for avoiding section collision for application server requests over a single database connection, the database server assigns query identifiers to each instance of the same cursor opened for the same processing level within an application, allowing multiple instances of the same cursor to be processed in parallel without section collision. The application server assigns a command source identifier to each statement sent over a single database connection to uniquely identify the application source of the statement. This applies for multiples of the same statement sent by different application sources within the same application, for a single statement containing multiple application sources, and for multiple statements from different applications multiplexed over a single database connection. These statements can be processed separately from and in parallel with the each other without section collision.

Computer-readable medium to multiplex multiple application server requests over a single database connection

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

In a method for avoiding section collision for application server requests over a single database connection, the database server assigns query identifiers to each instance of the same cursor opened for the same processing level within an application, allowing multiple instances of the same cursor to be processed in parallel without section collision. The application server assigns a command source identifier to each statement sent over a single database connection to uniquely identify the application source of the statement. This applies for multiples of the same statement sent by different application sources within the same application, for a single statement containing multiple application sources, and for multiple statements from different applications multiplexed over a single database connection. These statements can be processed separately from and in parallel with the each other without section collision.

Method and mechanism to multiplex multiple application server requests over a single database connection

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

Provided is a method, system, and program for implementing a database trigger. Upon detecting a trigger event, a determination is made of at least one row in a base table affected by the trigger event. For each column in the base table of a data type that is referenced in a triggered action associated with the trigger event, a reference is generated referencing the data of the data type. The reference is inserted in a transition table column including data of the data type from the affected row in the base table referenced in the triggered action. The reference is used to access the data of the data type when performing the triggered action.

Method, system, and program for implementing a database trigger

A method, apparatus, and article of manufacture for a computer-implemented apportioning system. Work is distributed to processors in a multi-processor system. Initially, during bind-time, a scaling factor is determined for each processor. The scaling factor represents relative processing power in relation to each other processor. Then, portions of a total amount of work are distributed to each processor based on the determined scaling factor of that processor and a determined amount of work for an average processor.

Apportioning a work unit to execute in parallel in a heterogeneous environment

A system and method for a computer system having a plurality of DBMS providing a coordinating and assisting function. If a DBMS performs a coordinating function, it is referred to as a coordinating DBMS. If a DBMS performs an assisting function, it is referred to as an assisting DBMS. Each coordinating DBMS receives a query from a user application, decomposes the query into multiple parallel tasks, and allocates the parallel tasks to all of the DBMSs in the system. Each assisting DBMS receives one or more parallel tasks from a coordinating DBMS, executes the parallel tasks and returns the results to the coordinating DBMS. The coordinating DBMSs and assisting DBMSs access one or more storage devices. Furthermore, the present invention comprises a system and method for dynamically disabling a parallel mode on the coordinating DBMSs and the assisting DBMSs.

Query parallelism in a shared data DBMS system

Growing community of inventors

Morgan Hill, CA, United States of America

Tammie Dang