Tracking inserts
concept brazil Updated Sep 10, 2026 1 min read c_TrackingInserts.md
By default, the system does not create Audit records for inserts because in a typical instance, inserts can account for over 80% of the size of the Audit table.
Not tracking inserts allows for better performance and a much smaller Audit table. Administrators can enable auditing of inserts by setting the glide.sys.audit_inserts property to true.
19 lines · 824 B
--- title: Tracking inserts description: By default, the system does not create Audit records for inserts because in a typical instance, inserts can account for over 80% of the size of the Audit table. locale: en-US canonical_url: https://www.servicenow.com/docs/r/platform-security/c\_TrackingInserts.html release: brazil topic_type: concept last_updated: "2026-09-10" reading_time_minutes: 1 breadcrumb: [Knowing about History sets, Auditing] --- # Tracking inserts By default, the system does not create Audit records for inserts because in a typical instance, inserts can account for over 80% of the size of the Audit table. Not tracking inserts allows for better performance and a much smaller Audit table. Administrators can enable auditing of inserts by setting the **glide.sys.audit\_inserts** property to true.
| title | Tracking inserts |
| description | By default, the system does not create Audit records for inserts because in a typical instance, inserts can account for over 80% of the size of the Audit table. |
| locale | en-US |
| canonical_url | https://www.servicenow.com/docs/r/platform-security/c\_TrackingInserts.html |
| release | brazil |
| topic_type | concept |
| last_updated | 2026-09-10 |
| reading_time_minutes | 1 |
| breadcrumb | Knowing about History setsAuditing |