Database Objects & Platform Features
The building blocks: tables, views, and the objects that turn Snowflake from a warehouse into a full application platform, streams, tasks, dynamic tables, stored procedures, UDFs, and semi-structured data. This closes out the COF-C03 domain map.
These topics belong to Domains 1 and 4 rather than forming their own block. Most of them come down to sorting: schema-level versus account-level objects, table types by cost and persistence, scalar versus tabular versus procedure. Semantics traps do the rest: a SELECT that doesn't consume a stream, a dynamic table you can't INSERT into, LAST_QUERY_ID(2) versus (-2). When an option names a command you've never seen in this guide, it probably doesn't exist.
Databases, Schemas & Tables
The object hierarchy every privilege, every grant, and every query path in Snowflake sits inside: account → database → schema → object.
Databases & Schemas
A database is a logical container for schemas; a schema is a logical container for tables, views, and every other object type. Every database ships with two schemas by default: PUBLIC, the default working schema, and INFORMATION_SCHEMA, a read-only, auto-populated set of metadata views and table functions describing the objects inside that specific database.
The object hierarchy, drawn precisely
Every Snowflake object lives at exactly one level of a strict containment hierarchy, and knowing each object's level is most of the skill. Warehouses feel like they should live inside a database. They don't. Pipes feel account-wide. They aren't. Learn the map, not the intuition.
database.schema.object. Read top to bottom: each level contains the next.A useful drill: take one object from each level and sort them. Pipes and file formats are schema objects, even though pipes drive account-wide ingestion. Resource monitors, warehouses, and storage integrations are account objects, even though you use them from inside a database context every day. And a fully qualified name always has exactly three parts for a schema object (database.schema.object), which is itself a giveaway: three parts means a schema object, two parts (db.schema or db.database_role) means a database-level object, and a bare name means an account object.
Sort these five: resource monitor, file format, virtual warehouse, pipe, storage integration. Only file format and pipe are schema objects. The other three are account-level, and every one of them is placed there deliberately because it either governs compute (warehouses, monitors) or holds credentials (integrations), things Snowflake refuses to scatter across databases.
CREATE DATABASE analytics_db; CREATE SCHEMA analytics_db. staging; CREATE SCHEMA analytics_db. marts WITH MANAGED ACCESS; -- only the schema owner (or MANAGE GRANTS) grants on objects here SELECT * FROM analytics_db. information_ schema. tables; SELECT * FROM TABLE(analytics_ db. information_ schema. query_ history( )) LIMIT 10; -- a table function, last 7 days
Information Schema vs Account Usage, precisely
| Information Schema | Account Usage | |
|---|---|---|
| Scope | Views: one database. Table functions such as QUERY_ | Entire account |
| Includes dropped objects | No | Yes |
| Retention | 7 days to 6 months, view-dependent | Up to 1 year on most views |
| Latency | Near real-time | 45 minutes to 3 hours, depending on the view (about 2 hours for most) |
| Where it lives | Inside each database (INFORMATION_ schema) | The shared SNOWFLAKE database |
SCHEMA INSIDE SALES_DBSALES_DB.
ACCOUNT
DATABASESALES_DB
DATABASEHR_DB
DATABASEOLD_DBdropped yesterday
SCHEMA IN THE SHARED SNOWFLAKE DATABASESNOWFLAKE.
The INFORMATION_SCHEMA of any given database exposes two kinds of objects: views for all objects contained in that specific database, and table functions for account-level, historical, or usage data (query history, login history, task history) that draw information beyond that one database's boundary.

