> 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/microsoft-fabric/limits-and-performance.md).

# Limits & performance

Set Fabric capacity, concurrency, and workload guardrails for reliable operations.

## Operational boundaries

### Compute sizing

Fabric Warehouse compute is tied to the workspace's assigned Fabric capacity (an F-SKU or trial capacity), not a per-query warehouse you resize yourself the way you would on Snowflake. Size the assigned capacity for your workload's concurrency and data volume at the Fabric-admin level; Vulcan has no lever to resize Fabric capacity from the project config.

### Concurrency

Start with `concurrent_tasks: 2` for daily incrementals. Because there are no explicit transactions and the overwrite strategy is DELETE\_INSERT rather than MERGE for time-range/partition kinds, avoid overlapping runs against the same table. A second run's `DELETE` can race a first run's `INSERT` with no transactional isolation to fall back on. Use `concurrencyPolicy: Forbid` for every scheduled workflow on this engine.

### Scheduling and latency floor

Schedule after upstream lands, set `timezone: UTC`, set `endOn` 1 to 2 years out, and use `concurrencyPolicy: Forbid`. The latency floor includes: warehouse SQL endpoint connection setup (Entra token acquisition plus ODBC connect), no index-assisted point lookups (every filtered query is closer to a scan than it would be on an indexed MSSQL table), and asynchronous warehouse creation/drop latency (seconds to tens of seconds) if your workflow provisions warehouses dynamically.

## Performance reference

Because there is no user-tunable indexing, sizing conversations for Fabric center on query shape and capacity tier rather than index design. Track plan/run duration per model, semantic query wall time, and rows touched per incremental window. When concurrency or latency degrades, fix in order: remove cross-join-shaped queries, pre-aggregate high-cardinality `COUNT(DISTINCT ...)` measures into a mart, stagger schedules so DELETE\_INSERT-based incrementals never overlap on the same table, then escalate the Fabric capacity tier as a platform-level change. Reproduce measurements against your own workspace capacity before quoting them externally. Fabric capacity tiers behave differently from a dedicated SQL Server instance under load.

### Next step

Use [Troubleshooting](https://v2.dataos.info/references/engine-guide/microsoft-fabric/troubleshooting.md) to diagnose connection, deployment, and runtime 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/microsoft-fabric/limits-and-performance.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.
