# Append Only

**URL:** <https://forum.inductiveautomation.com/t/append-only/3593>\
**Category:** Archived Topics\
**Created:** [November 11, 2011, 10:27pm UTC](https://forum.inductiveautomation.com/t/append-only/3593 "2011-11-11T22:27:10Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jsham](https://avatars.discourse-cdn.com/v4/letter/j/ac91a4/32.png) [@jsham](https://forum.inductiveautomation.com/u/jsham)\
**Post date:** [November 11, 2011, 10:27pm UTC](https://forum.inductiveautomation.com/t/append-only/3593/1 "2011-11-11T22:27:10Z")

</div>

I’m familiar with the archive engine in MySQL, including its limitation of “no keys allowed”, but how do you achieve a similar setup with MSSQL? Our preference would be to use the append-only feature of the archive engine with auditing to create a table that is more resistant to tampering for obvious reasons, but on the MSSQL platform. Any ideas?

---

<div class="post-metadata">

**Author:** ![Colby.Clegg](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/colby.clegg/32/3282_2.png) [@Colby.Clegg](https://forum.inductiveautomation.com/u/Colby.Clegg)\
**Post date:** [November 22, 2011, 1:28am UTC](https://forum.inductiveautomation.com/t/append-only/3593/2 "2011-11-22T01:28:42Z")

</div>

There isn’t exactly an out-of-the-box set of features that I’m aware of, but I’ve never really tried to set this up, so someone else might have a better suggestion. However, the first ideas that pop to mind for me:

1. Lock the table permissions down to only allow select for most users… and then perhaps create a special user for Ignition that is used for inserts.
2. Use triggers to audit changes (a quick search proved this seems to be a common enough approach. See [here](http://weblogs.asp.net/jgalloway/archive/2008/01/27/adding-simple-trigger-based-auditing-to-your-sql-server-database.aspx) for one example)

However… I’m afraid the trigger-audit method might be a little inefficient. With the importance of data integrity, especially for situations like those dictated by 21CFR11, I feel like I must be missing something that is likely new for SS 2005 or 2008. Hopefully others will post as well!

Good luck,