> For the complete documentation index, see [llms.txt](https://knowledgebase.qommentary.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.qommentary.com/qommentary-writeback/advanced/audit-trails/enable-audit-trails-for-database/sql-server-example.md).
# SQL Server example
This section shows how to set up audit trails for a SQL Server table.
The following Customers table will be used as a writeback destination table.
{% hint style="success" %}
This example assumes that you already have an existing extension using the Customers table as the destination table
{% endhint %}
To enable audit trails for the Customers table:
1\. Create a new table *Customers\_log* with the same structure as the writeback destination table and add the extra auditing columns
{% hint style="warning" %}
Note that the Id column (customer id) is not a primary key on this table since it will be duplicated on the *Customers\_log* table. If you want to assign an id for each audit row, you can add a RowId column and set it as an identity column.
{% endhint %}
2\. Go to the writeback extension in Qlik sense and enable logs
3\. Enter *Customers\_log* as the Audit log table name
4\. Go to your writeback extension, add a record and click on Save.
5\. Edit the existing record and click on Save
6\. Open the Customers\_log table
As you can see from the Customers\_log screenthost, Qommentary audits all changes made by users.
