> For the complete documentation index, see [llms.txt](https://v2.dataos.info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://v2.dataos.info/references/engine-guide.md).

# Engine guide

- [Engine Reference Guide](https://v2.dataos.info/references/engine-guide/engine-guide.md): The full per-engine technical reference for building and running a Data Product on each supported Vulcan engine in DataOS.
- [Snowflake](https://v2.dataos.info/references/engine-guide/snowflake.md): The full technical reference for building and running a Vulcan Data Product on Snowflake, covering connection, grants, materialization, operations, performance, and troubleshooting.
- [Permissions and grants](https://v2.dataos.info/references/engine-guide/snowflake/permissions-and-grants.md): Configure required Snowflake roles, grants, and DataOS access for Vulcan deployments.
- [Connect to Snowflake](https://v2.dataos.info/references/engine-guide/snowflake/connect-to-snowflake.md): Connect Vulcan to Snowflake using direct authentication or a DataOS Depot.
- [Materialization behavior](https://v2.dataos.info/references/engine-guide/snowflake/materialization-behavior.md): Understand how Vulcan model kinds map to native Snowflake operations.
- [Limits & Performance](https://v2.dataos.info/references/engine-guide/snowflake/limits-and-performance.md): Size Snowflake compute, control concurrency, manage costs, and plan for performance.
- [Troubleshooting](https://v2.dataos.info/references/engine-guide/snowflake/troubleshooting.md): Diagnose common Snowflake and Vulcan failures, then recover production workloads.
- [Recipes](https://v2.dataos.info/references/engine-guide/snowflake/recipes.md): Implement common Snowflake patterns with production-ready Vulcan recipes.
- [Dynamic Tables and Access Policies](https://v2.dataos.info/references/engine-guide/snowflake/recipes/build-a-snowflake-powered-data-product.md): Create a Snowflake Data Product with a Dynamic Table, column masking, and row access policies using Vulcan.
- [Use Snowpark Python Models](https://v2.dataos.info/references/engine-guide/snowflake/recipes/use-snowpark-python-models.md): Build and run an RFM customer-segmentation model with Snowpark Python on Snowflake.
- [Databricks](https://v2.dataos.info/references/engine-guide/databricks.md): The full technical reference for building and running a Vulcan Data Product on Databricks, covering connection, Unity Catalog grants, materialization, state store, operations, and troubleshooting.
- [Permissions and grants](https://v2.dataos.info/references/engine-guide/databricks/permissions-and-grants.md): Know about Unity Catalog grants and DataOS access for Databricks deployments.
- [Connect to Databricks](https://v2.dataos.info/references/engine-guide/databricks/connect-to-databricks.md): Configure direct and depot connections, external state storage, local development, and production deployment.
- [Materialization behavior](https://v2.dataos.info/references/engine-guide/databricks/materialization-behavior.md): Understand how Vulcan model kinds map to Delta Lake operations on Databricks.
- [Limits & Performance](https://v2.dataos.info/references/engine-guide/databricks/limits-and-performance.md): Configure Databricks warehouse sizing, concurrency, cost guardrails, and performance baselines for reliable production workloads.
- [Troubleshooting](https://v2.dataos.info/references/engine-guide/databricks/troubleshooting-databricks.md): Diagnose Databricks connection, warehouse, and state-store failures.
- [Postgres](https://v2.dataos.info/references/engine-guide/postgres.md): Configure, build, serve, and operate PostgreSQL-backed Vulcan Data Products.
- [Permissions and grants](https://v2.dataos.info/references/engine-guide/postgres/permissions-and-grants.md): Provision PostgreSQL and DataOS access before configuring or deploying a Data Product.
- [Connect to Postgres](https://v2.dataos.info/references/engine-guide/postgres/connect-to-postgres.md): Configure PostgreSQL gateways, develop locally with Docker, and prepare production deployment.
- [Materialization behavior](https://v2.dataos.info/references/engine-guide/postgres/materialization-behavior.md): Choose PostgreSQL model strategies and apply engine-specific model behavior.
- [Limits & performance](https://v2.dataos.info/references/engine-guide/postgres/limits-and-performance.md): Size, schedule, and tune PostgreSQL workloads for reliable production operations.
- [Troubleshooting](https://v2.dataos.info/references/engine-guide/postgres/troubleshooting.md): Diagnose PostgreSQL connection, permissions, model, and runtime failures.
- [Recipes](https://v2.dataos.info/references/engine-guide/postgres/recipes.md): Implement common PostgreSQL patterns with Vulcan.
- [Full-Text Search and Row-Level Security](https://v2.dataos.info/references/engine-guide/postgres/recipes/full-text-search-and-row-level-security.md): Build PostgreSQL search and access controls with full-text search and row-level security.
- [Spark](https://v2.dataos.info/references/engine-guide/spark-1.md): Technical guide to building and running a Vulcan Data Product on Apache Spark with Iceberg: connection setup, materialization, tuning, and troubleshooting.
- [Permissions and grants](https://v2.dataos.info/references/engine-guide/spark-1/permissions-and-grants.md): Provision DataOS, lakehouse, compute, state-store, storage, and Git access for Spark deployments.
- [Connect to Spark](https://v2.dataos.info/references/engine-guide/spark-1/connection-options.md): Configure the Vulcan gateway connection to Spark and load the JVM and   Python dependencies the driver and executors need.
- [Spark lakehouse limitations](https://v2.dataos.info/references/engine-guide/spark-1/spark-lakehouse-limitations.md): Constraints for Vulcan Spark and Iceberg lakehouse workloads.
- [Materialization behaviour](https://v2.dataos.info/references/engine-guide/spark-1/materialization-behaviour.md): Understand how Vulcan model kinds map to native Spark/Iceberg operations,   and how the semantic layer and business metrics build on top of them.
- [Limits & Performance](https://v2.dataos.info/references/engine-guide/spark-1/limits-and-performance.md): Size Spark workloads, tune execution, and set performance and cost guardrails.
- [Troubleshooting](https://v2.dataos.info/references/engine-guide/spark-1/troubleshooting.md): Diagnose Spark, Iceberg, dependency, deployment, and runtime failures.
- [Deployment recipes](https://v2.dataos.info/references/engine-guide/spark-1/deployment-recipes.md): Ready-to-copy sparkConf and resource sizing for common Spark deployment   shapes: daily incremental, medium lakehouse mart, large backfill, and   MERGE-heavy CDC.
- [Trino](https://v2.dataos.info/references/engine-guide/trino-1.md): The full technical reference for running a Vulcan Data Product on Trino, with three deployment shapes (dedicated managed Trino cluster, shared Minerva, and bring-your-own external Trino).
- [Dedicated Trino](https://v2.dataos.info/references/engine-guide/trino-1/dedicated-cluster.md): The full reference for the dedicated managed Trino cluster (vulcan-dg-trino), one cluster per Data Product, covering the deploy manifest, catalog priority, JVM tuning, and failure modes.
- [Cluster sizing and operations](https://v2.dataos.info/references/engine-guide/trino-1/dedicated-cluster/dedicated-cluster-sizing-and-operations.md): Configure fixed worker capacity, write targets, fault handling, and JVM memory for dedicated Trino.
- [Minerva](https://v2.dataos.info/references/engine-guide/trino-1/minerva-1.md): The full reference for connecting Vulcan to a shared, DataOS-managed Minerva (Trino) cluster, covering the secret and password generation, projection into config, and the connection setup.
- [External Trino](https://v2.dataos.info/references/engine-guide/trino-1/external-trino.md): The full reference for connecting Vulcan to a bring-your-own Trino, Starburst, or self-hosted cluster that exists outside DataOS, covering connection options, authentication, and catalog notes.
- [Starburst](https://v2.dataos.info/references/engine-guide/trino-1/external-trino/starburst.md): Build and run a Vulcan Data Product on Starburst Galaxy using a Trino-compatible external cluster, covering connection, deployment, materialization, operations, and troubleshooting.
- [Capabilities and limitations](https://v2.dataos.info/references/engine-guide/trino-1/capabilities-and-limitations.md): Confirm Trino catalog compatibility, model support, and view security before deployment.
- [SQL Server](https://v2.dataos.info/references/engine-guide/sql-server.md): The full technical reference for building and running a Vulcan Data Product on Microsoft SQL Server, covering connection, grants, materialization, local Docker setup, and troubleshooting.
- [Permissions and grants](https://v2.dataos.info/references/engine-guide/sql-server/permissions-and-grants.md): Provision SQL Server and DataOS access before configuring or deploying a Data Product.
- [Connect to SQL Server](https://v2.dataos.info/references/engine-guide/sql-server/connect-to-sql-server.md): Configure SQL Server gateways, develop locally with Docker, and prepare production deployment.
- [Materialization behavior](https://v2.dataos.info/references/engine-guide/sql-server/materialization-behavior.md): Choose SQL Server model strategies and apply engine-specific model behavior.
- [Limits & performance](https://v2.dataos.info/references/engine-guide/sql-server/limits-and-performance.md): Size, schedule, and tune SQL Server workloads for reliable production operations.
- [Troubleshooting](https://v2.dataos.info/references/engine-guide/sql-server/troubleshooting.md): Diagnose SQL Server connection, permissions, model, and runtime failures.
- [Microsoft Fabric](https://v2.dataos.info/references/engine-guide/microsoft-fabric.md): Technical reference for building and running Vulcan Data Products on Microsoft Fabric Warehouse, covering connection, authentication, materialization, and troubleshooting.
- [Permissions and grants](https://v2.dataos.info/references/engine-guide/microsoft-fabric/permissions-and-grants.md): Provision Fabric and DataOS access before configuring or deploying a Data Product.
- [Connect to Microsoft Fabric](https://v2.dataos.info/references/engine-guide/microsoft-fabric/connect-to-microsoft-fabric.md): Configure a Fabric gateway, develop against a dev warehouse, and prepare production deployment.
- [Materialization behavior](https://v2.dataos.info/references/engine-guide/microsoft-fabric/materialization-behavior.md): Choose Fabric model kinds and understand their native Warehouse behavior.
- [Limits & performance](https://v2.dataos.info/references/engine-guide/microsoft-fabric/limits-and-performance.md): Set Fabric capacity, concurrency, and workload guardrails for reliable operations.
- [Troubleshooting](https://v2.dataos.info/references/engine-guide/microsoft-fabric/troubleshooting.md): Diagnose Fabric connection, warehouse, materialization, and endpoint failures.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://v2.dataos.info/references/engine-guide.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.