"Keeping track of you data made easy"

Data management is one of the most youngest but most widely uses technology in the area of legal reporting. Many years tax authorities and judges communicated via paperwork. With the new digitalized world the paradigm of having a piece of paper in the hand that is unmodifiable had to be redefined. Many countries have laws that require to keep copies of eMails and tax related documents in a location that can not be altered. With paper this was a, relative, easy task. Just write it with special ink and then lock it away. In a world containing only ones and zeros the method of staring this type of data has changed. Software companies create many types of applications that try to prohibit the tampering of the original data. The format PDF is one of the most well known formats to store data that is hard to tamper. 

In the world of database systems database vendors try to offer a wide variety of methods to store the data in forms of history entries. E.g. with the help of binary logs an admin can determine the exact live cycle of every tuple in an MySQL database system. Binary logs require a large amount of space on the storage medium and for a restore operation to a specific point in time a large amount of DBA time is required. It is not possible to query historical data from the command line tool or from within an application.

The Revision Engine offers a native way to store data in different version while each version is retrievable with a simple SQL statement. The retrieval of historical data is based on a modification of the way data is stored within a storage engine. The Revision Engine is not a new storage engine type but a type of middle ware between the MySQL server and the existing storage engines. Furthermore data storage is organized in different types of schema with different performance metrics offering the DBA the most performance method for the table types. Since the Revision engine is visible to the MySQL server as a storage engine the DBA can decide for every table if the data should be versioned or not. 

For more information please read the White Paper or contact us at: This e-mail address is being protected from spambots. You need JavaScript enabled to view it

HatColorSoft provides support for all of our Projects.

Data versioning - This is the original use case where we simply wanted to version data for later retrieval

Consistent reporting views - A problem faced by many online reporting systems. How to show your manager the same number before and after a meeting in a live OLTP system

Data security compliance - Many industry related software systems require to version data. Such as production system for medication. Here we show how to efficiently version the data to be compliant with many laws and policies without letting your data explode.

Last Updated on Wednesday, 20 April 2011 22:56