Hi ...
The Stitch-in-Time product does employ journaling in a very clever way.
The product employs very small journal receivers.
Once a journal receiver for a particular observed file is full, it's detached and a
new journal receiver is attached. Then Stitch-in-Time processes the finished receiver,
discarding the unconstructive information and saving the audit-savvy data in a
database format inspired by the structure of the observed file.
Net result: Stitch-in-Time users don't have to worry about the well-known management
issues with journaling. When the auditor needs to know something, the data is
ready/set/go to answer auditing issues for critical observed files.
more info:
http://www.unbeatenpathintl.com/stitch_in_time/source/1.html
Warm regards,
Milt Habeck
Unbeaten Path
North America: (888) 874-8008
International: +(262) 681-3151
From: lgoodbar@xxxxxxxxxxxxxx
To: midrange-l@xxxxxxxxxxxx
Sent: Wednesday, November 19, 2008 9:43 AM
Subject: RE: Identifying who deleted records - trigger programs
<flippant>
Isn't that called journaling?
</flippant>
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Milt Habeck
Sent: Tuesday, November 18, 2008 12:27 PM
To: Midrange technical discussion group
Cc: Blake.Moorcroft@xxxxxxxxxx
Subject: Identifying who deleted records - trigger programs
When Stitch-in-Time is asked to observe a database, the product saves
the image of the
record just before a change and what the record looks like after the
change. Also saved:
who did it, precisely when that happened, and what tool was used to
execute the change.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/midrange-l.
midrange.com
