# Audit Logging

**URL:** <https://forum.inductiveautomation.com/t/audit-logging/6027>\
**Category:** Ignition\
**Created:** [March 13, 2013, 9:20pm UTC](https://forum.inductiveautomation.com/t/audit-logging/6027 "2013-03-13T21:20:19Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dustin.Phillips](https://avatars.discourse-cdn.com/v4/letter/d/45deac/32.png) [@Dustin.Phillips](https://forum.inductiveautomation.com/u/Dustin.Phillips)\
**Post date:** [March 13, 2013, 9:20pm UTC](https://forum.inductiveautomation.com/t/audit-logging/6027/1 "2013-03-13T21:20:19Z")

</div>

Currently my audit log is being over run by stored procedure entries. In any given day I can have 150k+ sproc calls. Is there any way I can stop these from being logged?:scratch:

Thanks!

---

<div class="post-metadata">

**Author:** ![Travis.Cox](https://avatars.discourse-cdn.com/v4/letter/t/b9bd4f/32.png) [@Travis.Cox](https://forum.inductiveautomation.com/u/Travis.Cox)\
**Post date:** [March 18, 2013, 9:03pm UTC](https://forum.inductiveautomation.com/t/audit-logging/6027/2 "2013-03-18T21:03:01Z")

</div>

You can bypass the audit log system using the system.db.runPrepUpdate funtion but we didn’t add that to the system.db.createSProcCall function. I will add a ticket in for that.

---

<div class="post-metadata">

**Author:** ![Carl.Gould](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/carl.gould/32/7262_2.png) [@Carl.Gould](https://forum.inductiveautomation.com/u/Carl.Gould)\
**Post date:** [April 2, 2013, 4:18pm UTC](https://forum.inductiveautomation.com/t/audit-logging/6027/3 "2013-04-02T16:18:36Z")

</div>

This has been added for 7.5.7