# Data Explorer

Paradime IDE's Data Explorer provides real-time data preview capabilities for your dbt™ models and SQL queries, allowing you to validate your transformations without running a full dbt™ compile.

### How It Works

Click the Data Explorer Tab in the [Command Panel](/app-help/documentation/code-ide/command-panel.md). Here you can:

* Preview Data (View model results)
* Download results as CSV
* Preview compiled SQL
* Preview specific SQL segments

{% @arcade/embed url="<https://app.arcade.software/share/hW14LmU2pQ88UZUlJ6Wo>" flowId="hW14LmU2pQ88UZUlJ6Wo" %}

***

### Compile & preview using production state (Defer to Production)

If you enable **Defer to Production** in the IDE, Data Explorer will compile and preview your models using the **production state** (the latest `manifest.json` from the production schedule you selected).

This is useful when you want to:

* Validate changes to a downstream model **without** rebuilding all upstream models in your dev schema.
* Preview results against production-like upstream relations while still iterating in development.

{% hint style="info" %}
When Defer to Production is enabled, both Data Explorer actions (**Preview Data** and **Compiled SQL**) will automatically defer to the selected production manifest/state.

For setup requirements and deeper details on how `--defer` works, see [Using Defer to Production in Paradime](/app-help/concepts/paradime-fundamentals/dbt-tm-defer-to-production.md) and ["Defer to Production" configuration](/app-help/documentation/bolt/managing-schedules/schedule-configurations.md#defer-to-production-configuration).
{% endhint %}

***

### Previewing Data

1. Open any SQL file in the editor
2. Click the Data Explorer icon in the command panel
3. Optional: Change the query row limit to your desired value (anywhere between 1-1000)
4. Click "Preview Data" to see your model's results
5. Review the compiled SQL and data output
6. Optional: Download the data returned in the preview as a .csv, click "Download CSV"

<figure><img src="/files/B5ZYeTYJlFT9565cyQnW" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
By default, Paradime automatically adds a `LIMIT 100` to the data preview. You can change this limit anywhere between 1 - 1000 by editing the text box next to "Query Limit"
{% endhint %}

***

### Previewing Compiled SQL

1. Click the Data Explorer icon in the [command panel](/app-help/documentation/code-ide/command-panel.md)
2. Click "Compiled SQL" to see your model's results
3. Review the compiled SQL to understand how your SQL, jinja, and macros unfold

<figure><img src="/files/LHphpiZGy8qG6KKc3qoU" alt=""><figcaption></figcaption></figure>

***

### Preview Specific SQL Segments

To preview only a portion of your model (like a CTE or subquery):

1. Highlight the desired SQL segment in your file
2. Click the Data Explorer icon in the command panel
3. Click "Preview Data" to see results for just that segment

<figure><img src="/files/9kPqyOcIhyPfn8zz8RJs" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
This is useful for testing individual CTEs or subqueries before running your entire model.
{% endhint %}

***

### Related Resources

[**Scratchpad**](/app-help/documentation/code-ide/additional-features/scratchpad.md) - Need a space for SQL experiments? Scratchpad provides a temporary environment for testing SQL and dbt™ queries without affecting your project files. Learn more about writing and testing queries in a dedicated, persistent workspace.


---

# Agent Instructions: 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:

```
GET https://docs.paradime.io/app-help/documentation/code-ide/command-panel/data-explorer.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.