# Empty or drop database tables

Open a database connection's table index to inspect table names, schema information, and available row counts. An unknown count is different from zero. Open a table to inspect its paged rows before changing it.

## Empty and drop have different effects

**Empty** removes rows but preserves the table structure. **Drop** removes the table itself. Dropping one table requires you to type its name; dropping a selected group requires the count-based phrase shown in the confirmation. Bulk Empty uses a destructive confirmation without the drop phrase.

Read the selected table names before confirming. A table expected by a writing workflow is not interchangeable with another table that has similar columns.

## Referencing workflows

A destructive operation can be blocked when enabled workflows still write to the table. The result identifies blocked tables and their workflow counts. Inspect those workflows and decide whether to disable, edit, or retain them before trying again.

Do not remove the connection to work around a dependency block without considering its other resources and users. A connection test answers access, not whether table removal is safe.

## Bulk outcomes

Bulk operations report each table's outcome in an aggregate summary. A table already absent counts as already gone for Drop, but it is reported distinctly for Empty because Empty promised to preserve the table. Successful and already completed items leave the selection; blocked and failed tables remain for investigation or retry.

A failure on one table does not undo changes already completed on another. Read the full result and refresh the table index before repeating the operation.

There is no Strive automatic undo for a dropped provider table in this experience. For editable tables belonging to an App, use [App table management](/docs/tables/tabs-and-management); those are separate resources.