Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.firebolt.io/llms.txt

Use this file to discover all available pages before exploring further.

Creates a new schema in the current database. Schemas are logical namespaces that organize tables, views, and other database objects. Every database includes a default schema named public. You can create additional schemas to separate and organize objects by function, team, or access level.

​
Syntax

CREATE SCHEMA [IF NOT EXISTS] <schema_name>

​
Parameters

ParameterDescription
IF NOT EXISTSPrevents an error if a schema with the same name already exists. Without this clause, the statement fails if the schema already exists.
<schema_name>The name of the schema to create. Must be unique within the database.
All identifiers are case-insensitive unless enclosed in double-quotes. For more information, see Object identifiers.

​
Examples

Create a schema 
CREATE SCHEMA analytics;
Create a schema only if it does not already exist 
CREATE SCHEMA IF NOT EXISTS staging;
Create objects within a schema After creating a schema, you can create tables, views, and other objects inside it by qualifying the object name with the schema: 
CREATE SCHEMA IF NOT EXISTS analytics;

CREATE TABLE analytics.events (
    event_id INTEGER,
    event_type TEXT,
    event_date DATE
);

CREATE VIEW analytics.recent_events AS
SELECT * FROM analytics.events WHERE event_date > '2025-01-01';
Reference objects using two-part and three-part identifiers You can reference objects using a two-part identifier (schema.object) when the database context is already set, or a three-part identifier (database.schema.object) to fully qualify the object across databases: 
USE DATABASE my_db;

SELECT * FROM analytics.events;

SELECT * FROM my_db.analytics.events;