is there a limit of audited fields that can be enabled in a table?

[Community Alums]

is there a limit of audited fields that can be enabled in a table?

[Community Alums]

and also is there a limit refering dates that get stored in this audited field????

[Bert_c1]

There is no limit that I'm aware of. One reason the sys_audit table is so large, but refer to:

AuditedTables documentation

[Mark Roethof · Accepted solution]

Hi there,

No there is not such a limit. Though can you mention the reason behind your question? Ideally you don't want to just use the old school method of just enabling audit on a table, nowadays ideally you would use the method of whitelisting or blacklisting fields for audit. So your audit is configured purposely, instead of simply turning it on or off. Unfortunately, this is something that hardly is being done at customers since this is with most implementations already not part of implementations. Main reasons lack of knowledge at consultancy companies + consultancy companies are not paid for this. 

[Its_Azar]

Hi there @Community Alums 

I guess, there is no explicit hard limit on the number of fields that can be audited for a table. However, auditing too many fields can have performance implications. When auditing is enabled, ServiceNow creates records in the audit history tables (sys_audit, sys_audit_delete, etc.) each time an audited field is changed. This can lead to majoe data growth and impact performance, especially for tables with a high volume of changes.

If this hepls kindly accept the answer thanks much.,