Models

Models represent a logical dataset — a distinct table structure (schema) derived by a series of operations applied to one or more data sources. You create Models for data assets you wish to deploy into Snowflake.

Models tie the Project Workbench into the Jobs Module via a Project Environment. This environment is treated as the Project's design environment. When working with Models in the Workbench, the Project Environment is always used for deploying Models.

Models are available as part of the Jobs module. To license the Jobs Module, contact sales.

Models vs Deployments

Models are a more flexible and comprehensive version of Datameer Deployments. Both contain the logic and configuration needed to create and update data assets inside Snowflake, but Models provide significantly more functionality and are designed for modern, complex Snowflake environments.

Capability	Models	Deployments
Deploy to multiple locations	✓	—
Versioned & tagged SQL code	✓	—
Advanced event-driven triggers	✓	—
Conditional triggers (source freshness / data quality)	✓	—
Per-job data source location override	✓	—
Incremental materialization	✓	—
Use as a data source in the Workbench	✓	—

When to use Models: For most teams, Models should replace Deployments. If you need to deploy data assets into multiple environments, require versioning, or need any of the capabilities listed above, use Models.

When to use Deployments: For simple projects — especially those with a single Snowflake environment — Deployments remain a good fit.

Migrating from Deployments to Models

If you are currently using Deployments and want to take advantage of Models, see Managing Model Jobs.