Join today’s webinar:
Successfully Execute DB2 Log Tracking Tasks

Relational DBMS have a transaction log for recovery purposes in case of failure. However, It has long been known that the information stored in the log is also well suited for other purposes. Think of correction, propagation and audit.

Log data, for example, shows which application or user changed the data, when it was changed and in what order. This facilitates regular review of relevant data changes. In case of undesirable data changes, it is possible to make corrections by using the log to create undo statements. This is often easier than trying to restore the data using image-copies. In addition, if an object has been accidentally deleted, it can be restored, or undropped, using information from the log. Another common usage of the log is forwarding data to other applications, for example, to a data warehouse. Plus, when compared to other approaches, log based replications are generally very efficient regarding CPU and storage consumption!

In short, the DB2 log is a potential gold mine. Although, in the past, available log analyzer tools were expensive and difficult to handle, that’s all changed now with ULT4DB2. Visit our webcast on April 2nd to learn how easy it is to audit changes, to forward data or just to see what was going on within a certain time frame. Reserve your free spot now.

Webinar: Successfully Execute DB2 Log Tracking Tasks
Date: Wednesday, April 2nd 2014
Time: 11.00 am PST / 2.00 pm EST