Statements

Preview Snowflake data definition (DDL), data manipulation (DML), transaction (TCL), and data control (DCL) statements in Snowflake compatibility mode.

Data definition language

Statement	Support	Notes
`CREATE TABLE`	Supported	Column-definition, `AS SELECT`, and `CLONE` forms, with `IF NOT EXISTS`, `TEMPORARY`, column constraints, and `DEFAULT`. `CLUSTER BY` becomes the table’s primary index, including a computed clustering key. `TRANSIENT` and `COMMENT` are accepted and ignored. `IDENTITY`, `AUTOINCREMENT`, `LIKE`, `DATA_RETENTION_TIME_IN_DAYS`, and the policy and Iceberg clauses are rejected. A column list must match the query’s output width. With `SELECT *` the width is not known when the statement is translated, so the list is not applied and the query’s own column names are kept, where Snowflake applies the declared ones.
`CREATE VIEW`	Supported	`OR REPLACE` and `IF NOT EXISTS`. `SECURE` is accepted and ignored: the view definition stays readable, where Snowflake hides it. Column-list views are not supported.
`CREATE SCHEMA`	Supported	`IF NOT EXISTS`. `TRANSIENT` is not supported.
`DROP TABLE`, `DROP VIEW`, `DROP SCHEMA`	Supported	`IF EXISTS`.
`ALTER TABLE`	With limitations	`ADD COLUMN`, `DROP COLUMN`, `RENAME COLUMN`, and `RENAME TO`. Not supported: `SET`/`UNSET COMMENT`, `ALTER COLUMN ... SET DATA TYPE`, `DROP NOT NULL`, `CLUSTER BY`, `ADD`/`DROP CONSTRAINT`, `SWAP WITH`, `SET`/`UNSET TAG`, and the retention settings.
`ALTER VIEW`, `ALTER SCHEMA`	Not supported	Neither `RENAME TO` nor `SET COMMENT` is accepted.
`CREATE SCHEMA ... CLONE`	Not supported	The objects in the source schema are not copied.
`CREATE DATABASE`, `DROP DATABASE`	Supported	`IF NOT EXISTS` and `IF EXISTS` are supported. Not supported: `OR REPLACE`, `CLONE`, the Snowflake platform options (`TRANSIENT`, retention, and so on), and `UNDROP`.
`USE DATABASE`	Supported	`USE <db>` and `USE DATABASE <db>` both switch the active database (client protocol 2.0+ required). `USE SCHEMA`, `USE WAREHOUSE`, and `USE ROLE` are not supported.
`SET`, `UNSET`	Not supported	Firebolt has no `SET` statement; its settings are passed as query parameters. Session variables and `$var` are not available.
`CREATE MATERIALIZED VIEW`	Not supported
`CREATE HYBRID TABLE`, `CREATE ICEBERG TABLE`, `CREATE EVENT TABLE`, `CREATE EXTERNAL TABLE`, `CREATE DYNAMIC TABLE`	Not supported
`CREATE FUNCTION`, `CREATE PROCEDURE`, `CALL`, `EXECUTE IMMEDIATE`	Not supported
`CREATE STAGE`, `CREATE FILE FORMAT`, `CREATE PIPE`, `PUT`, `GET`, `LIST`, `REMOVE`	Not supported
`CREATE STREAM`, `CREATE TASK`, `CREATE ALERT`, `CREATE SEQUENCE`	Not supported
`DESCRIBE`	Supported	`DESCRIBE`/`DESC TABLE` returns the column listing.
`SHOW`	Partial	`SHOW TABLES`, `SHOW VIEWS`, and `SHOW DATABASES` are supported, with the `LIKE`, `STARTS WITH`, `IN DATABASE`/`IN SCHEMA`, and `LIMIT` clauses (their columns follow Firebolt, not Snowflake). `SHOW SCHEMAS`/`SHOW OBJECTS` are not.
`COMMENT ON`	Not supported

Data manipulation language

Statement	Support	Notes
`INSERT`	Supported	`INSERT ... VALUES` and `INSERT ... SELECT`.
`UPDATE`	Supported	Including `UPDATE ... FROM`.
`DELETE`	Supported	Including `DELETE ... USING`.
`TRUNCATE TABLE`	Supported
`MERGE`	Supported	`WHEN MATCHED THEN UPDATE`/`DELETE` and `WHEN NOT MATCHED THEN INSERT`.
`INSERT OVERWRITE`, `INSERT ALL`	Not supported
`COPY INTO`	Not supported	Table and location forms.

Transaction control

Statement	Support	Notes
`BEGIN`	Supported	`BEGIN TRANSACTION` and `START TRANSACTION` are accepted synonyms.
`COMMIT`	Supported
`ROLLBACK`	Supported

Data control language

Roles and object privileges map onto Firebolt’s native access control. A Snowflake form with no Firebolt equivalent is rejected with an error rather than silently mistranslated, so a migrated script never grants more or less than it states.

Statement	Support	Notes
`CREATE ROLE`	Supported	`IF NOT EXISTS`. `CREATE DATABASE ROLE` is not supported.
`GRANT <privilege>`, `REVOKE <privilege>`	With limitations	`SELECT` (with an optional column list), `INSERT`, `UPDATE`, `DELETE`, `TRUNCATE`, `USAGE`, and `EXECUTE` (on a function), on a `TABLE`, `VIEW`, `DATABASE`, `SCHEMA`, or `FUNCTION`. The recipient is a role, given as `TO ROLE r`, a bare `TO r`, or `TO PUBLIC`.
`GRANT ROLE`, `REVOKE ROLE`	Supported	Role membership: `GRANT ROLE r TO ROLE`/`TO USER`.
`CREATE USER`, masking and row-access policies, tags	Not supported

The following are rejected with an error: GRANT ALL and GRANT MODIFY (Firebolt’s ALL and MODIFY both cover DROP, which Snowflake reserves for OWNERSHIP, so mapping either would grant more than Snowflake’s), OWNERSHIP and REFERENCES, ON ACCOUNT and other account-level privileges, ALL/FUTURE ... IN SCHEMA, granting a privilege directly to a user, and the WITH GRANT OPTION, GRANTED BY, AS GRANTOR, and CASCADE/RESTRICT modifiers. To grant on a table named account, quote the name.

Limitations

DDL returns no result set. Snowflake returns a status message such as Table T successfully created.
DML returns no result set. Snowflake returns the affected-row counts.
Fully qualified three-part database.schema.table names are not supported; see Query syntax.
Warehouses, ALTER SESSION, and session variables are not supported, nor are integrations, external volumes, shares, applications, Streamlit, Cortex services, and replication or failover groups.

Overview

Performance and Observability

Security

Self-Managed

Managed service

Guides

SQL reference

Release notes

API reference

Legal

Data definition language

Data manipulation language

Transaction control

Data control language

Limitations

​Data definition language

​Data manipulation language

​Transaction control

​Data control language

​Limitations

Data definition language

Data manipulation language

Transaction control

Data control language

Limitations