You’re offline. This is a read only version of the page.
65,271
Hi all,
I was wondering if anyone has developed a method to capture (and keep track of) changes made using the PSTL tool.
Everyone loves what it can do, but that lack of historical record keeping is a bit uncomfortable (especially for the auditors).
Kind regards
Leslie
*This post is locked for comments
Thanks Mahmoud,
Hey, a gal's got to dream!
I ended up creating a table that would populate as the tool ran. I have not read your link as yet, but I am betting it is something better that I can implement. Thank you for your help.
Kind regards,
Leslie
Even a SQL Server Profiler trace created with proper event selection can help.
If there were, I would have been blessed.
I have run into this issue recently while using the customer combiner utility, I desperately looked up for any documentation or reference that would make the process much more controlled and understood for audit purposes. Unfortunately, there was none.
Mr. Richard Wheeler has run into the same issue previously as well, looking for PSTL GL Account Change Audit Trail
As for me, I ended up creating few trigger on the db level to track the fields and changes for the "customer combiner" utility specifically in parallel with SQL profiling, the results were much more simple than I had imagined, my findings were published on following link; Customer Combiner Utility
The bottom line, few triggers could do the job. But still would be quite fortunate for any process flow documentation or history tracking tables.
Hope this helps at all,
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,253
Super User 2024 Season 2
#2
Martin Dráb
230,188
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (