|
Thanks to everyone who has added to this thread. The backup issue could be a problem for me as the file I need to do this on is one of our largest with 2.5M records. It gets backed up nightly so have 2.5M read triggers fire could cause a problem. My trigger could ignore that job and not journal (or data queue) that read but the trigger processing overhead would still take place. I could also remove the trigger just before backup starts and then put it back after backup ends but that's something I don't like to do as it could lead to problems someday when adding it back fails and the error is hidden deep in the backup joblog.
My other option is change code in the apps that read this data and presents it do a user (all in-house source code) and have each app journal the read.
And since I first asked this question nothing I do is going to meet the need 100%. I remembered that we send the data I need to read journal off to a could service that one of our offices use and the user can view the data that needs tracked from that service. I have no way to monitor or control access to the data once its sent.
Mike Cunningham
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.