Leyne, Sean wrote:

>
> SOX tracking of all data changes made in the context of a
> transaction/session/connection.

Well, then you would need some sort of Hi-Lo mechanism to keep number
sequence uninterrupted. For example we can introduce "database
generation" stored in db header. I would start at zero when db is
created, stored on backup and incremented by one on restore. Value
accessible via CURRENT_DB_GENERATION or whatever. That would give you
the "Hi" part, the "Lo" part would be the current transaction number.

Problem solved without database triggers.

What other problem can database trigger solve?

best regards
Pavel Cisar
IBPhoenix