The Settings tab of a Static table is where you deploy it, read its statistics and drop its stored data. The tabs across the top of the table are Static, Preview, Dependants and Settings; the table's setup lives on the Static tab.
The Settings tab fills in only after the table is saved and deployed. Until then it explains what is missing.
Nothing loads on the tab until the table is deployed: no statistics appear, and the Preview tab stays disabled until you deploy.
Deploying creates the table in the warehouse with your current column configuration.
| You see | What it means |
|---|---|
| Static table deployed successfully, with "The static table has been deployed to the warehouse" | The table is in the warehouse. The statistics start loading, and Preview opens. |
| Static table partially deployed | Only part of the deployment succeeded. The reason under the title describes the first failure. |
| Static table deployment failed, with "The static table could not be deployed." | The table was not deployed. Read the message, fix the problem, then click Deploy again. |
A Static table needs at least one column marked PK before it can deploy; see Static table columns. Troubleshooting lists the messages that can stop a deployment. Once the table is deployed, its Preview tab opens as well; see Preview table data.
The strip titled Static Table Statistics sits above Table Management. Three cards summarise the stored table:
A card shows - while its value is not available. Click Refresh to reload the numbers.
Drop removes the table's stored data and keeps its definition, so you can deploy it again into an empty table. The action sits in the statistics strip and appears only while the table is deployed.
After a drop the table is no longer deployed: it shows Pending in the tree again, Settings asks you to deploy it, and Preview stays disabled until you deploy it once more. If the drop fails, a message says what happened, and the dialog stays open so you can try again.
Dropping does not change the table's columns. See Static table columns for the rules that apply to the primary key and the table's other flags.
A drop cannot be undone. The stored rows are removed for good, and the table starts empty when it is deployed again.
Before you drop, open the Dependants tab to see what uses the table; Dependencies and dependants explains the list. Deploy, run, truncate and monitor tables covers the wider day-to-day actions.
Table Management sits under the statistics strip. Its Open General step link takes you back to the Static tab, on its General step, where the table's name, description, logical models and permission groups are set.
The table has not been saved yet. The line under the title reads Please save the static table first to view settings. Save the table first, then open Settings again.
The table is saved but not yet in the warehouse. Click Deploy in the banner at the top of the tab. Until the table is deployed, no statistics appear here.
Only part of the deployment succeeded. The reason under the title describes the first failure. Read it, fix the problem, then click Deploy again.
Yes. A drop keeps the table's definition, so the Deploy banner returns and you can deploy it again. The table starts empty; fill it from its Data Mapping step.
No. Drop removes the stored data and keeps the table's definition, so the table stays in place and can be deployed again. Deleting removes the table itself; see Deploy, run, truncate and monitor tables.
They are not dropped. They break until you fix them or deploy the table again. Check the Dependants tab before you drop; see Dependencies and dependants.
Preview needs a deployed table, and a drop removes the stored table from the warehouse, so the tab disables again, with the tooltip Table must be deployed to preview data. Deploy the table again to reopen it.
The value is not available yet. Click Refresh to reload the numbers.
Click Open General step under Table Management. It opens the Static tab on the General step.