Change Log Setup and Change Log Entry

(0) Share

Report

Posted on by mbr

5,136

Our company wants to perform audit trails on all mods/inserts/deletion of tables in Nav as we seem to be having problems with users making changes and causing problems for our Nav day to day business undertakings. So I enabled pretty much 90% of the tables to ensure we cover everything. Is this okay? I know we have to watch the growth of the sql server DB as this could cause the DB to grow exponentially. But since harddrive space is cheap, we are okay with it. We would just need to add more harddrive space and perhaps RAM if need be. Does anyone foresee any problems with turning on Change Log Entry and enabling audits on 90% of the tables? I gather since Nav has this feature, we could use it to full capacity. Are there any other precautions anyone wish to impart?

Please advise.

*This post is locked for comments

I have the same question (0)

All responses (4)

Answers (1)

Verified answer

Mohana Yadav 60,999 Super User 2025 Season 2 on at

Like (0)

Report

Change Log Entry table will grow too fast and same with database.

Performance may decrease.

Export and save the data from change log entry table to excel or some other.

and delete the data from change log entry table

Was this reply helpful? Yes No
Suggested answer

Tharanga Chandrasekara 23,118 on at

Like (0)

Report

It will definitely increase the size of the DB and performance of the NAV will decrease for a certain amount.

As a solution for that you can export old change log entries to a another DB or to a excel file and delete those entries. By doing that you will be able to decrease the size of NAV DB and increase the performance.

You can schedule SQL Server Agent to handle this. Once a month move all the change log entries to a separate DB table and delete the entries from NAV change log table.

If you want to save them in excel file then you can easily use NAV jobs to handle this.

(Create a XML port and export the data)

Was this reply helpful? Yes No
Suggested answer

Saurabh Shah 4,560 on at

Like (0)

Report

Hi,

Enabling Change log entries for many tables will definitely decrease the performance and also increase the size of database. sometimes it land up with the table lock entry issue which we had faced with one of our customer in past.

you can create one another SQL database with the same table as change log and then with the SQL script you can transfer all your change log record in it and delete the same from your production database. you can also automate by SQL as tharanga suggested.

I recommend to active the change log for only those tables and fields which are necessary to have a log instead to include all the fields of table.

Regards,

Saurabh Shah

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Thanks for all the suggestions.

I did backup the records to excel. But i'm facing this issue where the Change Log Entry table was locked by another user.

I tried restarting the instance as well. Still no luck.

What are your suggestions, Delete the records through SQL ?

i have around 6000000+ records

Was this reply helpful? Yes No