How does the Archive Database creation works (4294783)

Change Auditor has a set of rule in the Archive and Purge section of the Client which can be set to define the time when the database will be created:

- Year Start Month

This will determine the month the database will start receiving data

- Process events older than

This will determine when the events will be transferred from the main database to the archive

Archive Database Creation follows this logic:

1. First, it will check if there is an existing archive database
2. Next, it will check the newest event available to archive based on the current date, Year Start, and number of days specified in Process events older than
3. If there are events to be archived based on the times in step 2 and there is an existing archive database for the year of the newest event available to archive, then events will be copied to the archive. If there is no existing archive database for the year of the event available to archive, a database will be created.

Example #1

• Let's assume that we have a production database that has events from 2018 and 2019
• The current date is January 21, 2019, Year Start is January, and Process Event older than is 90 days
• If the archive job was created previously, there is already a ChangeAuditor_Archive_2018_January database created that 2018 events are being copied to
• When the archive job runs, it sees that the newest event to be archived is in October 2018 (current date - 90 days)
• Therefore, no new archive database needs to be created and the events are copied to the ChangeAuditor_Archive_2018_January

Example #2

• Let's assume that we have a production database that has events from 2018 and 2019
• The current date is January 21, 2019, Year Start is January, and Process Event older than is 14 days

• If the archive job was created previously, there is already a ChangeAuditor_Archive_2018_January database created that 2018 events are being copied to

• When the archive job runs, it sees that the newest event to be archived is January 7, 2018 (current date - 14 days)

• Therefore, any 2018 events are copied ChangeAuditor_Archive_2018_January and, since the newest event to be archived is in 2019, a new ChangeAuditor_Archive_2019_January database will be created and events from Jan.1, 2019 to Jan.7, 2019 will be copied to it