Below is the standard database purge configuration recommended by TZA. If you have any questions regarding the purge set up locally on your system, please contact ProTrack Support at protracksupport@tza.com.
| Database Table | Suggested Criteria | Comments | Active |
|---|---|---|---|
| wms_import_data | Delete records in status = 'COM' and created_date older than 60 days. | Yes | |
| time_attendance | Delete records in status = 'ADD' and swipe_date_time older than 2 days. | Should be purged periodically. | Yes |
| latency_info | Delete records with log time older than 30 days. | Performance tracking data that is non-critical to general reporting | Yes |
| trip_audit | Delete records older than 30 days. | Can be purged frequently because they can be re-generated by re-calc'ing the DI. | Yes |
| assignment_update | Delete records with created_date older than 30 days. | System audit trail for assignment status changes, used specifically for audit of system by TZA for problem resolution. | Yes |
| stdcalcerrorlog | Delete records with created_date older than 120 days. | System audit trail for TZA standards calculations. | Yes |
| scheduled_request | Delete records with topic = 'ADD_EOD' and status = 'IGN' and update_date older than 21 days. | Unnecessary entries that can be purged. | Yes |
| PTC.dbo.wms_raw_data | Delete records with created_date older than 30 days. | ProTrack Connect interface data. | Yes |
| PTC.dbo.wms_raw_data | Delete records with status = 'IGN' and created_date older than 1 day. | ProTrack Connect interface data for non-live facilities. | Yes |
| PTC.dbo.tanda_raw_data | Delete records with created_date older than 30 days. | ProTrack Connect interface data. | Yes |