Hi,
We have a read trigger based audit system to record who, when and why certain files were accessed because of legal requirements.
It has been running for many years but is now causing issues with jobs that process a large number of transactions using embedded SQL where each transaction may launch several nested SQL requests that read files that have a read trigger attached.
The problem appears to be that SQL decides not to use the more efficient SQE method in favour or CQE which does things like creating a copy for a table scan. This is making some jobs horrendously slow.
Redesigning the audit system to not use read triggers is beyond consideration. Unless there is some workaround that can force the use of SQE then we are faced with rewriting the SQL function points as native RPG where they access files that have read triggers.
Does anyone have any suggestions.
Peter
#####################################################################################
This correspondence is for the named person's use only. It may
contain confidential or legally privileged information, or both.
No confidentiality or privilege is waived or lost by any
mistransmission. If you receive this correspondence in error,
please immediately delete it from your system and notify the sender.
You must not disclose, copy or rely on any part of this correspondence
if you are not the intended recipient. Any views expressed in this
message are those of the individual sender, except where the sender
expressly, and with authority, states them to be the views of
Veda. If you need assistance, please contact Veda :-
Australia
http://www.veda.com.au/contact-us or New Zealand +64 9 367 6200
midrange.com
