> 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/sql-server/limits-and-performance.md).

# Limits & performance

Size, schedule, and tune SQL Server workloads for reliable production operations.

## Operational boundaries

### Compute sizing

A 2 to 4 vCPU, 4 to 8 GiB instance usually supports development. For first backfills, raise `tempdb` size and disk headroom. `SELECT * INTO` and bulk `MERGE` spill through `tempdb`.

Index the incremental `time_column` or `unique_key`. Size IOPS to write volume. For concurrent BI and the semantic API, watch connection count. Consider a connection pool.

### Concurrency

Start daily incrementals with `concurrent_tasks: 2`. Increase only when runtime is the bottleneck and the instance has connection and I/O headroom.

Each API replica consumes SQL Server connections. Pair replica increases with a pooler or more connection capacity.

### Scheduling and latency floor

Schedule after upstream data lands. Set `timezone: UTC`. Set `endOn` one to two years out. Use `concurrencyPolicy: Forbid` to prevent overlapping windows, connection pile-ups, and concurrent MERGE writers.

A provisioned instance has no cold start. Warm connections are typically sub-second. Unindexed filters scan tables. The first `SELECT * INTO` for a large FULL model is slower than later `TRUNCATE` plus `INSERT` runs.

## Performance reference

Measure active connections, model plan and run duration, semantic-query wall time, rows per incremental window, and index-seek versus table-scan ratio. Use `SET STATISTICS IO ON` and execution plans.

When concurrency degrades, act in this order:

1. Remove cross-join-shaped queries.
2. Add indexes on hot filter and join columns.
3. Add a connection pooler.
4. Size up the instance.
5. Investigate `tempdb` contention on bulk loads and MERGE.

Reproduce measurements on your own instance before quoting them externally.

### Next step

Use [Troubleshooting](https://v2.dataos.info/references/engine-guide/sql-server/troubleshooting.md) to diagnose failures and test recovery procedures.


---

# 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/sql-server/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.
