Share
ReportHI, is there any best practices on what to log in database log AX2009? I hnece o user acitivty on SO/PO and similar.
*This post is locked for comments
I have the same question (0)
You’re offline. This is a read only version of the page.
30
HI, is there any best practices on what to log in database log AX2009? I hnece o user acitivty on SO/PO and similar.
*This post is locked for comments
I have the same question (0)
My opinion is to log as little as possible, and target it to specific fields when you do. Appropriate use might be to log changes to a Customer's Credit Limit (one field), for example.
Logging changes to POs and SOs means turning on logging for a transactional type table, which is often cautioned against. That said, I have database logged some transactional tables in the area of output orders and shipments (when investigating a bug), and there was minimal impact. Logging was only enabled for a specific, short, period of time though.
The AX Support team wrote a blog about the performance impact of this functionality recently:
blogs.msdn.com/.../performance-impact-of-sysdatabaselog.aspx
All responses (
Answers (
