Delete a Computed Table
Delete a Computed Table from a JDBC source datastore.
Related
- Add a Computed Table to create a new one.
- Edit a Computed Table if you only need to change the query or description.
Before You Delete
Deleting a Computed Table is a hard delete. There is no archive step and no undo. Understand what goes with it before you confirm:
| What happens to... | Effect |
|---|---|
| The Computed Table itself | Deleted from the datastore. |
| Quality checks scoped to this container | Removed together with the container. |
| Anomalies raised against this container | Removed together with the container. |
| Profile history for this container | Removed together with the container. |
| Scan history for this container | Removed together with the container. |
| Base tables and views referenced in the query | Not affected. Only the metadata inside Qualytics is removed. |
Irreversible
Once a Computed Table is deleted, it cannot be recovered. If you want to keep the query for reference before deleting the container, copy it out of the Edit modal first.
When Delete Is Blocked
Deletion is blocked with 409 Conflict when quality checks in other containers reference this Computed Table through a configured reference container. The following rule types can trigger the block:
existsInnotExistsIndataDiffaggregationComparisonisReplicaOf(sunsetting; usedataDifffor new checks)
The error response lists the specific quality-check IDs that block the delete. Delete or repoint those checks first, then retry. See How It Works for the full delete-cascade rules.
Who Can Delete
| Team permission | Can delete? |
|---|---|
| Editor | |
| Author (owner) | |
| Any other team permission |
Steps
Step 1: Locate the Computed Table in the datastore's containers list and open its Bulk menu .

Step 2: A dropdown appears with the actions available for that Computed Table.

Step 3: Select Delete .

Step 4: A confirmation dialog appears listing what will be removed.

Step 5: Read the summary and confirm. The container is removed immediately, together with its quality checks, anomalies, profile history, and scan history.

Step 6: A success message confirms the deletion and the Computed Table no longer appears under the datastore.
