MySQL Archive Engine – Data Retention

I have spent the majority of my technology years in and around financial services dealing with issues of data security, retention, archiving and reporting. Though the finance sector is considered heavily regulated, so are other industries, such as health care and government.

Commercial database solutions have had a leg up on MySQL for some time in this area – however – MySQL is now joining the fray with tools to help anyone responsible for dealing with the sticky issues of data management.

The archive engine is as relevant for smaller web solutions as it is for the enterprise as it simplifies the DBA work involved in offloading data into an environment that limits interaction with data without sacrificing reporting capabilities.

Probably the single biggest difference from the existing compression features in MySQL is that one no longer needs to take a db offline to carryout exercises on data. Additionally, one can continue to insert data into archives, which is not feasible in existing MyISAM compressions.

Related posts:

1. Oracle and MySQL: Ally or Die? What will become of MySQL now Oracle has taken over...
2. EU to Investigate Oracle’s Acquisition of MySQL Here we go again. The European Commission will investigate the...
3. EU Object to Oracle’s MySQL Takeover Oracle's takeover of Sun Microsystems has been thrown into doubt...
4. MySQL Cross-Platform Table Naming Craig highlights the biggest potential pitfall of porting your MySQL-based...
5. Ready for PHP & MySQL Week at SitePoint? To celebrate the release of the new edition of well-loved...

This entry was posted on Friday, September 9th, 2005 at 1:14 am, contains 243 words, 6 images, and is filed under Open Source. You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed. The views and opinions in this blog post are those of its author.