Surety is performing system maintenance this weekend. Electronic date stamps on new Prior Art Database disclosures may be delayed.
Browse Prior Art Database

Method for tracking and validating access path elements in a database system.

IP.com Disclosure Number: IPCOM000127888D
Original Publication Date: 2005-Sep-13
Included in the Prior Art Database: 2005-Sep-13
Document File: 3 page(s) / 41K

Publishing Venue



Method for tracking and validating access path elements in a database system

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 43% of the total text.

Page 1 of 3

Method for tracking and validating access path elements in a database system .

Background: Database systems provide different capabilities at different levels of functionality, either due to enhancements or corrective service. A typical business environment has one or more of each type of the following systems: Development, Test, and Production. Each of these systems may be at different functional levels. Likewise, database systems provide different access paths as a means to indicate the execution flow the database system should take when retrieving/modifying data for a given SQL (Structured Query Language) statement. As application programs are developed on a database system, multiple versions of that program may be generated from different maintenance levels and access paths of the database system. Traditional practices allow the users to develop applications on one system and then deploy those applications to other systems. Deployment of applications across systems warrants a need for validating the database system may support those programs. Therefore, as a version of the program is executed on a given database system, the database system must support that version of the program. Often times the database system has maintenance level dependent logic throughout the entire database system in an effort to validate whether or not the database may support that program's version. Having a database system with such pervasive checking slows down execution of the application program and consumes more CPU. A method is being developed that will track and validate the program's versions during loading of a program by the database system where the checking can be performed in a single place using simplified logic, rather than during execution of said program where the checking is spread out across many modules and may require complex logic.

Problem: Since any database system may be at any maintenance level, logic in the database system must be introduced to validate the maintenance level functionality versus application program functionality. A method was designed to perform this functionality validation.

Solution: A method is being introduced to track which elements are built for a given access path and to validate the elements are supported for an SQL statement by the database system. When a database system processes an SQL statement, elements are created that represent the access path to be taken within the database system. These access path elements are stored in a package. Since a typical business environment hosts multiple types of systems for Development, Test, and Production and each of these systems may be at different maintenance levels, the database systems need a method for validating the programs may run on its' system. The method being introduced will record the level of the element being built and validate, during program loading, that the database system can support that level of the element. By introducing a method for tra...