> For the complete documentation index, see [llms.txt](https://docs.graph.build/EGeX4aTAJLlpg9Hh8kfl/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.graph.build/EGeX4aTAJLlpg9Hh8kfl/graph.build-studio/sql-iteration-for-large-dataset-transformations.md).

# SQL Iteration for Large Dataset Transformations

When working with large datasets for transformations, **Iteration** can be used to break the process into smaller chunks, enabling more efficient processing. The SQL Transformer also supports multi-threading, allowing different threads to process separate iterations simultaneously, significantly speeding up transformations. To enable iteration, check the tick box at the bottom of the query window.

<figure><img src="/files/F9knIDhL95NEpkGZTAPr" alt="" width="237"><figcaption></figcaption></figure>

This will display the iteration settings window, which includes two fields: **SQL Limit** and **SQL Offset**.

* **SQL Limit** specifies the number of rows each iteration will contain.
* **SQL Offset** determines the number of rows from the start of the dataset that will be skipped in the transformation.

<figure><img src="/files/OsYd6B5N1yaO5IjKI9fh" alt="" width="563"><figcaption></figcaption></figure>

&#x20;

For example, if a table contains 1,000,000 rows, the data can be split into chunks of 100,000 rows, with the first 200,000 rows ignored. In this case, the transformation will be divided into eight iterations of 100,000 rows each, resulting in eight separate RDF files.

**Note**: Iteration cannot be used with queries that already include **LIMIT** or **OFFSET** clauses. These keywords must be removed before enabling iteration.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.graph.build/EGeX4aTAJLlpg9Hh8kfl/graph.build-studio/sql-iteration-for-large-dataset-transformations.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
