Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik and ServiceNow Partner to Bring Trusted Enterprise Context into AI-Powered Workflows. Learn More!
cancel
Showing results for 
Search instead for 
Did you mean: 
RZYX
Contributor
Contributor

How long the data will be kept in Audit Table?

When using store change in Audit Table, how long the data will be kept in Audit Table? Any automatic maintenance or housekeeping of the data inside the table? 

Labels (1)
3 Replies
SushilKumar
Support
Support

Hello Team,

Audit tables are populated when task starts. whenever Task is stopped gracefully to start again or start from the time stamp, they created again. 

 

Reagrds,

Sushil Kumar

SachinB
Support
Support

Hello @RZYX 


Thank you for reaching out to the Qlik community!

We do have only below option when select Audit table as part of store change. 

Audit table creation:

If audit table exists when the target is reloaded: Select one of the following to determine how you want to handle the Audit table when the target is reloaded:

  • DROP and CREATE audit table: The Audit table is dropped and a new table is created in its place.
  • ARCHIVE and CREATE audit table: A copy of the existing table will be saved to the same schema before the new table is created. The archived table name will be appended with a timestamp, indicating when the archiving operation occurred (e.g. attrep_audit_table_20170605175601).

    Information note

    Currently this option is only available for the Hadoop target endpoint.

  • Delete old changes and store new changes in existing audit table: Data is truncated and added without affecting the Audit table metadata.
  • Keep old changes and store new changes in existing audit table: Data and metadata of the existing Audit table are not affected.


    Using an Audit table.

Regards,

Sachin B

 

 

 

 

RZYX
Contributor
Contributor
Author

Hello everyone,

Thanks for the response.

I have  seen the options as described by SachinB.

However, for our use case we will be running the task perpetually since the database is being updated by online transaction processing. So, we need the task to run perpetually to monitor changes in the database and update the Audit Table accordingly. 

Thanks