Re: Journaling not practical?!?!

["Colin Williams" <colinwilliams007@xxxxxxxxx>]

Heres a for instance.

Typically in a non journalled environment, you may have a program bug, or
maybe a data setup issue in your database that causes a program to fall
over, and leave records in your database that are not really valid because a
transaction did not complete.

In a journalled environment, you can code your application so that if
transactions do not complete, the system will auto-magically tidy up that
mess, by rolling back the incomplete transaction when an error occurs.

Or lets say something as simple as someone turning off their terminal/pc in
the middle of a transaction, journalling combined with comittment control
would ensure that incomplete transaction are not left in your database

Journalling also gives you an audit trail of what went on in your database,
that can be used for all sorts of purposes.

I would always recommend journalling. Yes, theres an overhead, and extra
work in the app to make use of commitment control and establish transaction
boundaries, but really journalling forces you to do what really should be
doing anyway.

How do companies manage the data integrity issues without the use of
journalling?


On 28/03/06, Evan Harris <spanner@xxxxxxxxxx> wrote:
>
> Hi Colin
>
> I'm curious as to what data corruption problems journalling would
> automatically fix.
>
> Regards
> Evan Harris
>
> At 05:05 a.m. 29/03/2006, you wrote:
> >I would have thought the fact that the database is large is more reason
> to
> >use journalling, not less, as it implies they have more to lose if the
> data
> >gets corrupted.
> >
> >They must be spending a lot of time using manual hacks to fix data
> >corruption problems, that are fixed auto-magically when you have
> journalling
>
> --
> 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.
>
>