Skip to main content
Use the SDKs or SQL to manage catalog objects, including tables, namespaces and views. The tables below provide a quick reference to the available methods; each object’s guide covers its setup and behavior. Some long-running operations also provide a submission method that returns a job. See the operation’s guide for how to track completion.

​
Management APIs

SQL is available through the Enterprise Flight SQL endpoint. See SQL.

​
Namespaces

See Namespaces.

​
Tables

See Tables for creating one and shaping its schema.

​
Materialized views

Local list_materialized_views reads table schemas to find views. On Enterprise, it requests the server’s view listing.
See Materialized views for creating one, and Refresh a materialized view for keeping it current.

​
Views

Enterprise Views exist only on an Enterprise cluster that enables them; the SDK methods send the view’s SQL query to the deployment. See Views.

​
Functions

Enterprise A function runs on the server, and only on a deployment that enables functions, so there is no local form. The TypeScript SDK has no function methods; use Python or SQL. See Functions.

​
Jobs

See Job Framework.

​
Indexes

SQL CREATE INDEX covers one column and takes no user-chosen name: the server names it. For a multi-column or named index, use the SDK.
Indexes are a performance decision rather than a structural one, so they are covered under Maintenance.

​
Work within a namespace

Most connection-level operations take a namespace_path (namespacePath) to act inside a namespace rather than at the database root:
In SQL the path is written as a $-joined schema instead; see Namespace for why it isn’t dotted.

​
Delete catalog objects

drop_table removes the table and every version of it. Table versioning does not survive the table being dropped, and neither drop_database nor drop_all_tables asks for confirmation.
Dropping a view removes only the saved query. Dropping a materialized view removes stored rows, because a materialized view is a table.