> For the complete documentation index, see [llms.txt](https://docs.e6data.com/query-engine/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.e6data.com/query-engine/get-started/quickstart/run-first-query.md).

# Run first query

Run your first real query in e6data after setup - open the SQL Editor, pick a cluster and catalog, and confirm results.

Once your workspace is set up - a catalog connected and a cluster running - run a query to confirm everything works end to end.

## Run a query

1. Open the workspace's Compute Plane and go to the **SQL Editor**.
2. In the Query Action Bar, select your **catalog**, **database**, and **cluster**.
3. Enter a query and click **Run** (or press `Cmd/Ctrl + Enter`):

   ```sql
   SHOW DATABASES;
   SELECT * FROM your_schema.your_table LIMIT 10;
   ```
4. Confirm results appear in the results pane below the editor.

{% hint style="info" %}
If your cluster is suspended, the first query resumes it automatically.
{% endhint %}

If results return, your deployment is working: the cluster reached your catalog's metadata and read your data in place.

## If the query fails

* An access error usually means the engine can't read your storage - recheck the cloud access you granted during setup.
* A connection or schema error usually points to the catalog - re-open it and use **Test Connection**.
* A timeout may mean the cluster is under-provisioned or the query is heavy - see [Cluster sizing and scaling](/query-engine/guides/clusters/cluster-sizing-and-scaling.md).

## Where to next

* **Secure your workspace** - configure SSO, roles, and access control: [Identity and RBAC](/query-engine/guides/security/identity-and-rbac.md).
* **Connect a BI tool** - point Tableau and other tools at your cluster: [BI tool recipes](/query-engine/developers/bi-tool-recipes/tableau.md).


---

# 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.e6data.com/query-engine/get-started/quickstart/run-first-query.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.