System Elegance

Users don't understand why it costs so much to expand the primary production database. It's because there isn't just one database. That database has a hot standby, and it's copied to a static start of day database, and a reporting database, and end of day, end of month and end of year images. You almost certainly create your test databases by loading a production image, and you probably create your development databases the same way. When the primary grows, so do all the copies.

The primary database always grows, as market data is rolled to the next day, and trades are updated and saved. Even if a trade is cancelled or matured, it just grows a little bit!

The System Elegance Archiver strips out all of the old data from your primary database: the cancelled and matured trades, the old versions of trades from years ago and the unused market data and stores it in an archive database. Your primary database shrinks. So do all the copies. Smaller databases need less storage, and are cheaper to run.

The System Elegance Archiver creates a third, view database to unify the datasets in the primary and archive database. Despite it's tiny size, the view database contains a complete Summit environment, containing all of the data in both the primary and archive databases. You can log onto it and run SQL queries just like you would in a normal Summit database. You can also run any Summit reports against the database, and even start up the Summit FT Front end. All of your archived data is online and accessible in exactly the same way that you would access live data.

The System Elegance Archiver knows all about Summit metadata.

The program scans the metadata to ensure that all of your trade extensions are archived along with the rest of the trade.

It knows how to update the archive database when you update your metadata in your in house release cycles.

See the Archiver page for more in depth coverage..