A table serves no data until it is deployed. This page covers deploying a table from its popup, the state it shows until then, and the actions and figures that appear once it exists in the warehouse.
While a table is not deployed, its popup shows a banner with a Deploy action.
Until then, tabs whose content needs the stored table show Table Not Deployed in place of their content: a plain card with an icon, the title and a line on what deploying unlocks, and no actions of its own.
Table popups share this banner and card; Shared elements in table popups collects them with the other common pieces.
The Settings tab gathers the table's actions into a strip of small buttons, such as Synchronize and Truncate. Two details matter day to day:
For what each action does and when to use it, see Deploy, run, truncate and monitor tables.
Truncate removes data from the table, and the table itself stays, with its definition and columns in place.
Partition support needs a partition key. When the table has none, the popup explains that partitions are not supported and why, rather than showing an error.
Drop removes the stored table but keeps its definition, so the table returns to the not deployed state and can be deployed again. Dropping a table that is not deployed changes nothing.
The drop and delete flows, with their confirmations, are on Drop and delete tables safely.
The popup reports the stored table's figures: Rows, Partitions and Size. Refresh them to read the current values.
The popup keeps a history of the table's query-settings revisions, with the newest first. The history is available once the table is saved.
The table's definition exists, but the table itself is not deployed yet, so content that needs the stored table stays closed. Click Deploy in the popup banner; the tabs open when the deploy finishes.
The deploy is running. The action stays disabled while it works, so wait for it to finish; content that needs the table opens afterwards.
It cannot run in the table's current state, and a tooltip on it says why. Point at the action to read the reason.
The action is running. Its icon shows a spinner and the button stays disabled until the work is done.
No. Truncate removes data, and the table itself stays with its definition and columns. Drop is the action that removes the stored table, and even then the definition stays, so the table can be deployed again.
Nothing. Dropping a table that is not deployed changes nothing, and the definition stays. On a deployed table, Drop removes the stored table and returns it to the not deployed state. See Drop and delete tables safely.
Partition support needs a partition key, and the table has none, so partitions are not supported for it. The popup gives the reason instead of showing an error, so this is expected for that table.
Refresh the figures: Rows, Partitions and Size update when you refresh them.
Yes. Put the cursor on a table name and press Ctrl+B (⌘+B on a Mac); the table opens in its popup. Open object editors lists the other ways to open objects.
Yes, for a saved table: the popup keeps a history of the query-settings revisions, with the newest first.