Browse Prior Art Database

Complete database change management process based on enforced and verified reverse operations trail

IP.com Disclosure Number: IPCOM000234708D
Publication Date: 2014-Jan-30
Document File: 2 page(s) / 27K

Publishing Venue

The IP.com Prior Art Database

Abstract

A software implementation of full database change management process based on reverse operations trail with quality assurance. Proposed software implementation of full database change management system requires for each change to produce and evaluate reverse operation. The change is evaluated positively when sequence of do and reverse operations results in no changes.

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

Page 01 of 2

Complete database change management process based on enforced and verified reverse operations trail

The objective of change management is to ensure that standardized methods and procedures are used for efficient and promptly handling of all changes to control IT infrastructure, in order to minimize the number and impact of any related incidents upon service. The problem occurs when database is maintained for a long time and volume of changes increases significantly.

Known change management tools allows to:


• Manually entry and track changes in external systems (ticketing system)


• Automatically monitor database activities (transaction log)

However, when any change needs to be reverted, known solutions only allow to revert all the changes since point of time, rather than reverting selective changes. An example of current solutions is restoring of database backup. It is proposed to have a software implementation of full database change management process based on reverse operations trail with quality assurance. Proposed software implementation of full database change management system requires for each change to produce and evaluate reverse operation. The change is evaluated positively when sequence of do and reverse operations results in no changes.

Main components of the system:

1. Change controller - change controller tracks and reports changes performed with reverse operations.

2. Change server - keeps knowledge base about changes and its reverse operations. Knowledge base has implemented map of atomic operations with known reverse equivalents. Server collects changes reported by each change controller.

3. Change sandbox - cloned resources required to evaluate the sequence of change and reverse operation.

Detailed scenario of full change management system:


1. Change controller monitors database operations


2. User starts database operations


3. Change controller tracks each operation before it's execution

1. If operation is known (found in knowledge base on change server), the reverse operation is already given in knowledge base

2. If operation is unknown, the change controller suspends operation execution and user is asked by controller to provide reverse operation specification

4. Collected change and reverse operations are evaluated for newly provided reverse procedures

1. Change sandbox is created with cloned resources required to evaluate the sequence of change and reverse operations


2. The sequence of...