> 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/managing-queries.md). # Managing queries This page describes how to manage and control queries against Kafka in Lenses SQL Studio. ## Termination Control ```sql SELECT * FROM topicA WHERE _key.deviceId=123 LIMIT 10 ``` Adding a **LIMIT 10** in the SQL query will result in the SQL terminating early, as soon as 10 x messages have been discovered. It’s not a perfect solution as we might never find 10 x messages, and thus perform a full scan. You can also set a maximum query or idle time: ``` SET max.query.time = 30s; ``` or max idle time, the idea is that there is no reason to keep polling if we have exhausted the entire topic: ``` SET max.idle.time = 5s; ``` or a maximum amount of data to read from Kafka. This controls how much data to read from Kafka **NOT** the required memory. ``` SET max.size = 1M; ``` ## Recent queries Recent queries are displayed, but only for the current session, they are not currently retained. Click on the play button to run a previous query. If a query is already running, you will be asked if you want to stop it first. **View All queries** ```sql SHOW ALL QUERIES ``` **View Running queries** You can see all running queries by Lenses users using SQL: ```sql SHOW QUERIES ``` ## Kill Running queries You can force stop a query by another user using SQL: ```sql KILL QUERY ``` \ Concurrent queries limit ------------------------ Starting with 6.1.3 version, there's a global limit on concurrent queries, as well as a limit per user. They can be set via the agent configuration: ``` lenses.sql.settings.max.concurrent.queries=200 lenses.sql.settings.max.concurrent.queries.per.user=2 ``` --- # 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/managing-queries.md?ask=&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.