> 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/resources/vulcan/models/data-models/types.md).

# Types

SQL, Python, and external model types, and how to choose between them.

Vulcan supports multiple model types for different execution patterns.

Choose the type that matches how you define, execute, and maintain your data.

## What this section covers

Use this section when you need to:

* decide between SQL and Python models
* reference data that Vulcan does not manage
* understand the tradeoffs between model definitions

## Quick selection guide

Start with **SQL models** for most projects.

Use **Python models** when SQL is not enough.

Use **External models** when you need metadata for tables outside the project.

## Compare model types

| Type       | Best for                                            | Managed by Vulcan | Query required |
| ---------- | --------------------------------------------------- | :---------------: | :------------: |
| `SQL`      | Standard transformations and warehouse-native logic |        Yes        |       Yes      |
| `Python`   | API calls, ML workflows, complex procedural logic   |        Yes        |       No       |
| `EXTERNAL` | Schema metadata for external tables                 |         No        |       No       |

{% hint style="info" %}
Most projects rely mainly on SQL models. Add other types only when they solve a specific need.
{% endhint %}

## Choose a model type

<table data-view="cards"><thead><tr><th></th><th data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>SQL models</strong><br>Use SQL files for most transformations, scheduling, and materialization patterns.</td><td><a href="https://v2.dataos.info/references/resources/vulcan/models/data-models/types/sql.md">SQL models</a></td></tr><tr><td><strong>Python models</strong><br>Use Python when you need custom logic, external libraries, or DataFrame APIs.</td><td><a href="https://v2.dataos.info/references/resources/vulcan/models/data-models/types/python.md">Python models</a></td></tr><tr><td><strong>External models</strong><br>Describe external table schemas so Vulcan can reason about lineage and optimization.</td><td><a href="https://v2.dataos.info/references/resources/vulcan/models/data-models/types/external-models.md">External models</a></td></tr></tbody></table>

## Common decision points

Quick criteria for picking between SQL, Python, and External models.

### Choose SQL models when

* the transformation is naturally expressed in SQL
* you want broad engine support
* you need standard Vulcan model behavior

### Choose Python models when

* the logic depends on Python libraries or APIs
* DataFrame code is clearer than SQL
* you can define schemas and dependencies explicitly

### Choose External models when

* the source table already exists outside Vulcan
* you need schema metadata, not lifecycle management
* you want better lineage for external dependencies

## Best practices

Prefer SQL models unless you clearly need Python.

Keep external model definitions accurate, because Vulcan relies on them as metadata contracts.


---

# 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/resources/vulcan/models/data-models/types.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.
