Database storage grows over time and impacts performance. Of course, you can add indexes and update statistics, but at some point in, if the table space size exceeds several TB, it is highly recommended to archive your data.
Deleting records is on regulated industries such as banking no option. Therefore, to remain compliant with regulations and maintain a healthy database performance, archiving is highly recommended.
Archiving examines files for records to be archived, writes the selected records (and any associated records) to an archive file (which should reside on a separate disc or possibly a separate machine accessible via a network), and then deletes the records. Archiving in T24 Transact is designed to reclaim space by moving historical data that is no longer required.
Archiving is run on one set of files at a time. There is a separate record for each set of files to be archived, the ids of which can be found in section 0 FILES.
Before running archiving, you should decide
what data is in scope
where archived files are stored
Enter this information into the ARCHIVE record for the files to be archived. If data is to be archived, files will be created with a $ARC suffix in the archive directory.
For example, if special entry files are to be archived, files will be created as RE.CONSOL.SPEC.ENTRY$ARC and RE.CONSOL.SPEC.ENTRY.KEY$ARC. The layout of the ARC files will be the same as the live files, with concatenated files being recreated as necessary. By default, the $ARC files will be created with the same type and modulus as the corresponding live files. However, if, for example, only half the data is expected to be archived, it may be desirable to create the $ARC file with a smaller modulus than the live file. This information should be entered into the archive record.
Timing of the Archiving Process
It is recommended that the archiving process be run after the end of the day has been completed but before users are allowed to sign on. However, since archiving removes data that is no longer needed, it can be done while the system is being used.
Compiling/Cataloguing programs
If it is thought that the data that is going to be archived may be needed in the future for reporting purposes, then before starting the archive, ensure that the database has programs cataloged locally. The database can then be restored at a later date and reports run using the data.
Backups and Archive record
Changing the directory and taking a backup of the folder are required.
For each of the sets of files for which archiving is to be run, there is a record in the ARCHIVE file. There are three distinct sections to the record. The first contains the main data of the record and is used to specify such things as the purge date or retention period, whether data is to be removed or archived, and if so, where the archived data is to be stored.
The Archiving Steps in T24 Transact
Ensure that the record in ARCHIVE for the files that need to be archived is authorized.
Create a record in ARC.GENERIC. REQUEST from the ID SYSTEM, then enter the ID of the previously created record (step 1) and verify.
Modify the field SERVICE.START TSA with CONTROL.SERVICE application for the ID TSM (ARC.SPECIAL IDs are not required). The entry and the ARC.CATEGORIES after verifying ARC.GENERIC, set entry to start automatically. In Step 2, make a request record.
How does your archiving approach look like?
Keep up the great work! Happy Performance Engineering!