Re: FieldProc Error - column has returned invalid data on a Zoned Numeric column

I should suggest that physical file triggers are an alternative to field
procedures for encoding data upon write and update events and decoding data
upon read events. This would also improve performance in cases where you
need to encode multiple fields; You can copy fields from the record buffer
into a data structure, then encode the data structure, and visa versa. You
reduce the number of procedure calls as well as reduce the number of calls
to encryption routines.

Our shop has adopted the use of database event handlers as alternatives to
triggers, which I'll share a link:

http://rd.radile.com/rdweb/info2/ibmiapp04.html

Our practice is to place data validation, referential integrity checks, and
business rules into service programs that export on_read() on_write()
on_update() and on_delete() procedures. We normally generate a database
event handler for every new table in our database. It would be pretty easy
to set the encrypt key value during the on_init() procedure. Decode
on_read(). Encode on_write() and on_update().







On Mon, Mar 30, 2020 at 7:16 AM Nathan Hughes <nathan.hughes@xxxxxxxxxxxxx>
wrote:

First, I want to thank everyone who has contributed to this, you all have
been immensely helpful with this issue! I've been able to make some
headway in this, and what I'm noticing is a drastic increase in time it
takes to read records. I knew that there would be a performance hit, but 8
times as long!? Has anyone else noticed this?

I know this is off topic, but does anyone know if enabled TDE (transparent
data encryption) on the ASP level is any better? Or worse?