> For the complete documentation index, see [llms.txt](https://docs.autonmis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.autonmis.com/mastering-data-queries-with-sql-editor/writing-and-running-sql-queries.md).
# Writing and Running SQL Queries
Upon entering the SQL Editor, the left-side navigation panel displays the database structure, including available **Schemas** and **Tables**. Users can:
1. Select a **schema** from the dropdown.
2. Use the **search bar** to locate tables within the schema.
SQL queries can then be written in the editor, and upon clicking **Run Query**, the query results are displayed in a table format under the **Data** tab in the 'Visualize' section.
To create a **Dashboard** using SQL Editor, the user can click on this [**link**](https://docs.autonmis.com/create-and-manage-your-first-dashboard/create-dashboards-from-sql-editor-or-sql-notebook/using-sql-editor).
{% hint style="success" %}
**AI Copilot:** Autonmis offers an AI assistant, accessed via the pencil icon, to help with query generation and suggestions.
{% endhint %}
---
# 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.autonmis.com/mastering-data-queries-with-sql-editor/writing-and-running-sql-queries.md?ask=&goal=
```
`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.