Browse Prior Art Database

Method and Apparatus for Detecting Abnormal DB Schema Changes Disclosure Number: IPCOM000245879D
Publication Date: 2016-Apr-15
Document File: 7 page(s) / 242K

Publishing Venue

The Prior Art Database


The majority of today’s information systems heavily depend on relational databases. Among all the factors that impact the functionality of information systems, abnormal database schema change is one of the key factors. This document discloses a pattern-based method and apparatus to detect abnormal changes on DB schema while the database evolves.

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

Page 01 of 7

Method and Apparatus for Detecting Abnormal DB Schema Changes


-Database plays a very important role in today's software architecture database is commonly used by website content management system, commercial banking system or any other software system related with data.
-The system starts in a "desired state" and then changes its states over time due to daily execution, maintenance, and updates. Some changes evolves the "desired state". But some are trouble makers.
-System/application failure is prevalent. Many service providers and companies are experienced a number outages which affected millions of their customers. And it could cause great commercial loss[1].

-Abnormal DB changes on the configuration, schema, and data caused by human errors, mis-configurations, or even the malicious intrusion is one of the root cause to these failures.

-e.g. in one banking customer, they met an over 2-hour application outage due to mis-drop table column -Database evolution is commonly occurred to satisfy new demands of the software, Wikipedia's database evolves 171 times in about 5 years, but only 22% of the query can adapt to the evolution throughout the history[2][3]

There needs a drift detection tool to identify abnormal changes on DB configurations and schema.


However, it is very hard to identify the problematic DB changes in the problem troubleshooting, because · The inherent complexity of database system, including numerous complicated features, like key constraint and index etc. Improper use could result in errors · In DB, to ensure data could be operate strictly, numerous data properties are integrated, like data scale, length, default value, with improper ope...