Troubleshooting Deleting User Archive Rows Older Than 30 Days

Delete user-archive records by passing a date-based filter to uaArchiveDelete. The available C-script uses DATEDIFF with CURRENT_TIMESTAMP and removes rows whose calculated age is greater than 30 days.

Deletion expression

uaArchiveDelete(hArchive, "datediff(day,date_field,current_timestamp) > 30 ");

hArchive identifies the open user archive, while date_field must be replaced by the archive column containing each record's date. The filter compares that value with the database server's current timestamp.

Boundary and data requirements

The strict greater-than operator does not match a result equal to 30. If the requirement means “30 days old or older,” review whether the predicate should use >= 30; confirm the desired boundary before changing the production archive.

Execute and verify the cleanup

1. Confirm that hArchive references the intended user archive.
2. Confirm that date_field contains valid date/time values and that the SQL engine accepts the shown DATEDIFF and CURRENT_TIMESTAMP syntax.
3. Run the uaArchiveDelete call with the filter.
4. Inspect the remaining archive rows around the 30-day boundary. Verify that newer rows remain and that rows matching the predicate were removed.

The evidence does not identify the runtime version, database engine, date format, return value, or error-handling interface. Test the predicate on noncritical archive data first, especially if the installation uses locale-dependent date handling.

FAQ