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.
Step by step, with screenshots
Set up Database log setup1 screen
Use this page to keep an auditable record of changes to tables that hold sensitive information.
Screen 1
Review the database log setup
Go to System administration > Setup > Database log > Database log setup
Review which tables are logged and for which type of change
Select New to open the Logging database changes wizard
Choose the tables or fields to log and the types of change
Select Finish to complete the wizard
Show the full screen page title tab to open what to set or check
Steps from Microsoft
Go to System administration > Setup > Database log > Database log setup.
Select New to open the Logging database changes wizard.
Choose the tables or fields to log and the types of change.
Log specific fields on tables that hold sensitive data rather than whole tables, with a plan for how long logs are kept and a cleanup job per companyLearn recommends logging specific fields to limit log entries and improve performance, and planning retention and cleanup because the log table grows quickly.
What should be logged?Logging busy tables: logging turns set-based operations into row-based ones and can slow long processes such as inventory close, BOM calculation, master planning and data imports.Test: Field change is logged
Feature management and licence
Licence or add-in
On this system the page opens for Information technology manager. By default the system logs all transactions that use electronic signatures. No Feature management feature needs to be turned on for this page.
You choose tables and fields for the whole environment database; the log entries it writes are cleaned up per company, because an administrator must set up a cleanup job per company. Microsoft Learn
Can it be undone
Reversible: Logging can be changed at any time. Log cleanup deletes log records, except records that are electronically signed.
If you change it later
Logging a table turns its set-based operations into row-based ones and makes the log grow, which can slow long-running processes; log specific fields where you can. Microsoft Learn
Technical architect
6Technical
Menu item
SysDatabaseLogSetupChecked in Dynamics 365
Form
SysDatabaseLogSetupChecked in Dynamics 365
Table
DatabaseLogShown as “Database logs” in Record infoChecked in Dynamics 365
Who can open it
PrivilegesMaintain database log setup SysDatabaseLogSetupMaintainDutiesMaintain system settings SysServerSettingsMaintain1 security roleInformation technology manager SysServerITManagerChecked in Dynamics 365
Roles to set it up and use it
To set it up or change 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 page
Options: Personalize, Page options, Edit, ShareChecked in Dynamics 365
Load order: Set up logging with the Logging database changes wizard in each environment, then run Consistency check so the log triggers match the setup.Microsoft Learn
Checked in a working Dynamics 365 system, version 10.0.49: the menu item, form, table and security, the page, the demo records and the values in the screenshots.
To cite this step: SA-SETUP-280, Set up Database log setup. Beyond ERP Atlas Hub, 2026-11-11. https://www.beyonderp.cloud/atlas/step/SA-SETUP-280