Custom Table Deep Dive: Archive Tables

[Jake Gillespie]

In the lifecycle of any enterprise system, data accumulation is inevitable. While active records are crucial for daily operations, driving workflows, reporting, and business processes, the sheer volume of historical data can eventually degrade system performance, slow down queries, and complicate maintenance. This is where Archive Tables become a critical architectural component in maintaining both data integrity and operational efficiency within the Now Platform.

Custom Table Disclaimer

The creation and usage of custom tables is directly tied to ServiceNow subscription entitlements. The articles I've written in relation to custom tables are based on the ServiceNow Custom Table Guide, which is available via the Legal Schedules -> Entitlement Supplements page. I strongly recommend seeking guidance from the ServiceNow Accounts team as licensing rules, entitlement SKUs, and specific limits can change over time. At the time of writing, this version became effective October 17, 2025.

What Are Archive Tables?
An Archive Table is not a table that an administrator creates manually; rather, it is a structure automatically generated by the ServiceNow data archiving process itself. These tables are designed specifically to house historical records that have been moved out of their primary, active business tables. For instance, when records from the core Incident [incident] table reach a defined age or status threshold, they can be migrated and stored in an associated Archive Table, such as Archive Incident [ar_incident].

The Architectural Advantage: Why Use Archiving?
The fundamental purpose of using Archive Tables is to decouple historical data storage from active system performance. By moving old records into these dedicated structures, the primary business tables remain lean, fast, and highly responsive for current operational tasks. This separation ensures that critical processes (such as Incident Management or Request Management) do not suffer performance issues due to millions of legacy entries.

The Exempt Status: A Licensing Consideration
From a licensing perspective, Archive Tables hold a unique position. They are classified as Exempt Tables, as per the ServiceNow Custom Table Guide. This means they are customer-created tables that do not count against your overall Custom Table usage limit or require specific entitlements from ServiceNow. This exemption is granted because the functionality (e.g., automated retention and archival process) is deemed essential for maintaining system health and compliance within the platform.

When Should You Rely on Archiving?
You should leverage the archiving feature when:

1. Data Retention Policies Mandate It: If your organisation has regulatory or business requirements to retain data for a specific period (e.g., seven years), but that data is no longer needed for daily operational queries, archiving is the ideal solution.
2. Performance Degradation is Observed: When reporting times become sluggish or database query performance dips due to table size, implementing an archival strategy can provide immediate relief by reducing the active dataset footprint.
3. Historical Auditing is Required: Archive tables allow you to maintain a complete historical audit trail of records without cluttering your live environment.

In essence, Archive Tables are ServiceNow's OOTB solution for managing data longevity. They ensure that while your organisation retains its valuable history, the platform itself remains agile and performant for today’s business needs.