Purge TagNet Data
This function enables Tag Event logging and other transactional data to be purged from the TagNet Repository. Over time event data can grow considerably slowing down performance of various TagNet operations as well as reporting.
Note: To enable this purge features you must setup this Binding that includes installing a SQL Stored Procedure. |
On or Before Date |
|
Enter the date you want data to be purged equal to or older than the date entered -or- the Cutoff Days below |
|
|
Cutoff Number of Days |
|
Enter the number of days you want data to be retained. For example: if entering 120 days then 4 months of data will be kept from the current date and the rest (older than that date) will be purged |
|
|
Inventory Transactions |
|
Selecting this check box purges Transaction History data (RFDLOCIH file) based on the [On or Before date] -or- [Cutoff Number of days] selected above. The purged records are written to an archive file (RFDLOHAR). Note this could take some time based on many records are in that transaction file so it is best to plan this purge off hours. |
|
|
Physical Inventory |
|
Selecting this check box will purge all Closed Physical Inventory Sessions based on the [On or Before date] -or- [Cutoff Number of days] selected above |
|
|
Reader Log |
|
Selecting this check box purges base tag event logging. Note that the purge does not archive the data as this is transitory low level logging. Note this could take some time based on many records are in that transaction file so it is best to plan this purge off hours. |
Update |
|
This button simply updates the settings that are looked at when the purge job runs from Scheduled Tasks. |
|
|
Copyright © 2024 Stratum Global, Inc.