BeyondERP.Newsletter
Menu

Setup step on the Database Log page · System administration

Read and clean up the database log

Use the log to answer who changed what, and keep it small with regular clean-up.

Used by
Information technology manager
Business process
Administer system features
Menu item
SysDatabaseLog
Main table
SysDataBaseLog
Data entity
SysDatabaseLogEntity
Setup steps
1 on this page
Show what matters for
SETUP GUIDEHow to set it up8 sections. Choose a role to highlight what matters to you.
Everyone

1What it is and why

What it isAn inquiry page that shows the changes recorded by database logging for the tables and fields that are set up to be logged.
What you do hereUse this page to review tracked inserts, updates, deletes and key renames, and to clean up or check the database log.
ExampleFor example, a BEAT controller asks who changed a vendor's bank account last week; the log, filtered on the table and the date, shows the update with the old value, the new value and the user.
Database Log page in Dynamics 365
The page in Dynamics 365. page title tab to open what to set or check
Functional consultant · Solution architect

2Where it fits

Business processAdminister system features
Menu pathSystem administration › Inquiries › Database › Database Log
Set up firstDatabase log setup Microsoft Learn
Used next byDatabase log cleanup Microsoft Learn
Related pagesDatabase log parameters Microsoft Learn
In this process Check the database connection · Check the daily index defragmentation
End user · Functional consultant

3How to do it

About the examples: Examples and screenshots in this guide use BEAT, a demo company in a Dynamics 365 test environment. Use your own company's codes and values instead of copying them.

Setup steps on this page

Read and clean up the database log

Use the log to answer who changed what, and keep it small with regular clean-up.

Steps from Microsoft

  1. Go to System administration > Inquiries > Database > Database log.
  2. Filter on Table name and Created date and time to find the change.
  3. Read the user, the type of change and the old and new values of the logged fields.
  4. From a record, use Record info > Database log to see the history of that record only.
  5. To delete old logs, select Clean up log and choose by table, by type of log, or by creation date and time.
  6. To repair missing or orphaned log triggers, select Consistency check.

Source: Microsoft Learn

Fields on the page

FieldWhat it meansExample
Table nameThe table whose record changed.Microsoft Learn Vendors
Type of changeInsert, update, delete or rename key.Microsoft Learn Update
Created byThe user who made the change.Microsoft Learn
Created date and timeWhen the change was made.Microsoft Learn

Common errors and fixes

MessageWhat to do
A change isn't in the logLogging was not set up for that table and field, or the log was cleaned up. Check Database log setup. Microsoft Learn

Test checklist

  1. Turn on logging for one field in Database log setup.
  2. Change that field on a record.
  3. Open the Database log and check the change shows the old and new value and your user.

Source: Microsoft Learn

Functional consultant

4Setup decisions

Setup stepRecommended value and whyDecision, common mistake and test
Read and clean up the database logLog only the tables and fields auditors need, and clean up entries older than the audit retention outside business hoursEvery logged change writes a row, so a broad log slows processing and grows the database; clean-up keeps it in check.How long are database log entries kept?Cleaning up all logs including the period auditors still need.Test: A logged change appears

Feature management and licence

Licence or add-inOn this system the page opens for Information technology manager. No Feature management feature needs to be turned on for this page.

Microsoft Learn

Solution architect

5Design impact

Shared or per companyPer company: each legal entity has its own records. Microsoft data model
Can it be undoneCan't be undone: Clean up log deletes entries for good.
If you change it laterLog records that are electronically signed can't be deleted, and cleanup has to be set up for each company. Microsoft Learn
Technical architect

6Technical

Menu itemSysDatabaseLog Checked in Dynamics 365
FormSysDatabaseLog Checked in Dynamics 365
TableSysDataBaseLogShown as “Database Log” in Record infoChecked in Dynamics 365
Data entitiesSysDatabaseLogEntityDatabase log Checked in Dynamics 365
Who can open itPrivilegesView database log SysDatabaseLogViewDutiesMaintain system settings SysServerSettingsMaintain
1 security roleInformation technology manager SysServerITManager
Checked in Dynamics 365
Roles to set it up and use itTo use itInformation technology manager SysServerITManagerGive people one of these roles. On this system, 1 role can open this page.Checked in Dynamics 365
Actions on the pageOptions: Personalize, Page options, Edit, ShareChecked in Dynamics 365
Developer

7Developer

Open it by URLhttps://<your-environment>/?mi=SysDatabaseLog
Integrate withSysDatabaseLogEntity data entity Checked in Dynamics 365
Data migrationSysDatabaseLogEntity (Database log): per company; not in Microsoft's default templates.Load order: Database log entries are the change history of each environment. Export them only to archive; don't import them into a new environment.Checked in Dynamics 365
Table definitionSysDataBaseLog columns and relations Microsoft data model
Everyone

8Sources

To cite this step: SA-INQ-540, Read and clean up the database log. Beyond ERP Atlas Hub, 2026-11-11. https://www.beyonderp.cloud/atlas/step/SA-INQ-540