What a run keeps, and for how long

What every run stores, how long it stays, and the audit trail.

In short

Every run keeps what ran (secrets masked), its timing, row counts, the result's shape, the verdict and the error - but never row values. Run details are kept 30 days, and every run writes a line in the project's audit trail.

Before you start

• Who: anyone who can open the project reads its runs.
• Plan: every plan.
• First: nothing to set up. There is no storage choice to make.

What is stored

See rows again

1. Open the test.
2. Press "Run" (or "Run now" in the editor).
3. Read the rows on screen while the result is open.

Good to know

• There is no storage choice to make: what every run keeps is enough for verdicts, drift and history.
• A project keeps the details of its runs for 30 days. Scratchpad runs are kept 30 days.
• Clearing old runs never removes the newest passing run of a test in each environment.
• Every run, refusal, connection test, catalog sync and load test writes a line in the audit trail with who, when, which environment and which tier.

Related

• /help/sql-tester/what-changed
• /help/sql-tester/safety-tiers-and-load-testing
• /help/sql-tester/reading-a-result