Reduce MySQL Results Database Storage Usage

Use this procedure when the AIQ results database is consuming excessive storage. Treat database cleanup as a controlled maintenance task because deleting execution data can permanently remove historical evidence and reports.

Before making changes

Confirm the affected MySQL instance, schema, and available disk space.
Create a verified backup or snapshot before deleting or archiving results.
Confirm the retention window with the customer or project owner.
Prefer supported AIQ cleanup, archival, or retention settings before using direct database changes.

Recommended cleanup workflow

Identify the largest result tables and the date range that can be archived or removed.
Export any reports or evidence that must be retained.
Run cleanup in a maintenance window with AIQ services stopped or quiesced if required by the procedure.
Optimize or analyze tables only after the cleanup approach has been validated.
Restart services and verify that recent executions, reports, and login flows still work.

Warning: Do not run broad delete statements without an approved backup and an exact retention target.

Last updated: October 8, 2026