> For the complete documentation index, see [llms.txt](https://docs.lenses.io/latest/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lenses.io/latest/devx/6.1/user-guide/sql-studio/limit-and-sampling.md).

# Limit & Sampling

This page describes how to limit return and sample data in Kafka with Lenses SQL Studio.

## Limit the output <a href="#limit-the-output" id="limit-the-output"></a>

To limit the output of the query you can use two approaches:

* use the `LIMIT` clause
* set the max size of the data to be returned

```sql
-- limit to 1 record
SELECT *
FROM groceries
LIMIT 1

-- set the data size returned to be 1 megabyte.
SET max.size="1m";

-- on the small dataset we have here 1 MB will accommodate all records added and more
SELECT *
FROM groceries
```

## Set a time limit for a query <a href="#set-a-time-limit-for-a-query" id="set-a-time-limit-for-a-query"></a>

To restrict the time to run the query, use `SET max.query.time`:

```sql
SET  max.query.time = '1h';

SELECT ...
FROM table
LIMIT 1000
```

## Sampling data <a href="#sampling-data" id="sampling-data"></a>

To sample data and discard the first rows:

```sql
SELECT *
FROM groceries
LIMIT 1,2
```

This statement instructs Lenses to skip the first record matched and then sample the next two.


---

# 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://docs.lenses.io/latest/devx/6.1/user-guide/sql-studio/limit-and-sampling.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.