Browse Prior Art Database

System for Conditional Execution of Structured Language Artifacts

IP.com Disclosure Number: IPCOM000243541D
Publication Date: 2015-Sep-30
Document File: 5 page(s) / 161K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a method to allow benign changes to influence the execution of structured language artifacts without affecting main functionality. The proposed method first checks for existing database objects in order to alleviate issues that arise from attempting to recreate said objects.

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

Page 01 of 5

System for Conditional Execution of Structured Language Artifacts


Most enterprise applications rely on deployment of resources on multiple tiers for successful operation . For high-traffic environments, processes must update these resources in a time-critical manner so that user traffic is not adversely impacted. Database resource deployment must include careful actions to ensure that no data integrity issues arise . For these reasons, organizations guard database resource or object updates with various levels of redundancy (i.e., database backup image made, traffic diverted to a mirror site, updates performed on resources and then traffic diverted back when updates are complete , etc.).

When issues occur in the update process, it is sometimes difficult to ascertain which updates successfully applied and which require reapplication. Current processes protect against such issues by restoring the backup image; this resolves any problematic issues and re-applies the update. However, the process of creating a backup image and restoring it (perhaps multiple times until the issue is resolved) extends the amount of time that systems must divert traffic from the environment .

Typically, the uncertainty that leads to the re-application of the database backup image is a result of the creation of database objects. If the objects already exist from a previous invocation of the update process, then attempting to recreate said objects results in an error, which further interferes with the completion of the update process.

One known method for resolving database-specific issues pertaining to creating objects that already exist is to use procedural SQL constructs to check for the presence of database objects before creating said objects . This is simple enough, but requires knowledge of these constructs for each given database type. Additionally, not all database types support procedural SQL. Hence, procedural SQL is not universally applicable.

A method is needed to resolve the errors resulting from the attempts to recreate already -existing objects, thus eliminating the need to restore database backups, and allowing the update process to re-run until complete.

Making functional changes to the constructs of systems that operate on legacy code is risky because legacy systems rely on the consistency and reliability that unchanged systems offer. Such systems are durable because of thorough testing and debugging prior to deployment and the lack of changes made since then.

The novel contribution is a method to allow benign changes to influence the execution of structured language artifacts without affecting main functionality. The proposed method first checks for existing database objects in order to alleviate issues that arise from attempting to recreate said objects. Additionally, it provides a universally usable (i.e. for all database types) Application

1


Page 02 of 5

Programming Interface (API) to check for the existence of database objects.

Asid...