Skip to content

Delete Datastore

Deleting a datastore removes its configuration and tracked records from Qualytics. It does not delete the physical tables or files in your infrastructure, including data already written to an enrichment destination. You need the Admin role.

Cascading Deletion

Deleting a datastore is permanent and irreversible within Qualytics. The following tracked information will be removed:

  • Container and field records representing its tables, views, and file patterns
  • All quality checks associated with the datastore, including comparative checks in other datastores that reference it
  • All anomalies across every table in the datastore
  • All scheduled operations for the datastore
  • All tag associations and team-datastore links

Before removing the records, Qualytics asks every operation of the datastore that is still Queued or Running to abort, so that work on a datastore that no longer exists stops. The deletion goes ahead even when one of those abort requests cannot be delivered, so check the Activity tab of a busy datastore before deleting it if you need to be sure its runs have ended.

If this datastore is an enrichment destination, deletion also unlinks every source that writes to it and resets each source's remediation strategy to None. Those sources can still be scanned, but cannot write enrichment output or run Materialize or Export until another destination is linked.

Qualytics also blocks the deletion while a Computed Join in another datastore uses one of this datastore's tables or files. The message names every such join, with its id and the datastore it belongs to; delete those joins first. Joins inside the datastore being deleted do not block it, since they are deleted with it.

Qualytics blocks the deletion while a flow action runs an operation on this datastore (for example a Scan or Export action that targets it) or a Global Export action writes to it. Remove or retarget those actions first. For an enrichment destination, also remove the scheduled Materialize/Export operations and flow actions on its linked sources that depend on the destination.

A flow that only names the datastore in its trigger's Source Datastores, or in an action's datastore filter, does not block the deletion. The datastore is taken out of that filter. If it was the only datastore in the filter, the filter becomes empty, which means every datastore:

  • An emptied trigger filter makes the flow start on events from every datastore.
  • An emptied action filter makes the action apply to every datastore. For example, an action that archives or deletes anomalies then reaches matching anomalies in all of them. The action's other filters, such as tags or statuses, still apply.

Update those flows before deleting. To stop writes from only one source without deleting the destination, unlink enrichment.

Steps

Step 1: Navigate to your datastore overview and click the Settings button located at the top-right corner of the interface.

Step 2: A dropdown menu will appear. Click on Delete to initiate the deletion.

Step 3: A Delete Datastore dialog appears, listing everything that will be permanently removed.

Step 4: Type the datastore name in the confirmation field to confirm the deletion.

Step 5: Click the I'm sure, delete this datastore button to confirm.

Step 6: A success message will confirm that the datastore has been successfully deleted. You will be redirected to the Datastores listing.