This page is an interface inventory: the text here is the text on screen, literally.
Where it is: menu Data → Console (address /dados). The screen title is
Data, and the subtitle says the main thing: "Write, run and see the result of
your SQL queries — with a cost per run. Every query is billed."
It's the screen for people who know (or are learning) SQL and want to look at the datalake tables directly. If you'd rather write the question in plain language, use the Queries screen.
The other data screens#
Until 10/03/2026, this page covered seven screens on its own. Now each screen has its own:
Console (/dados)
This page: SQL with cost per run.
Your datalake (/datalake)
The three layers (Bronze, Silver, Gold) and where the data lives.
Queries (/query)
A question in plain language becomes SQL, with an estimated cost.
Lineage and impact (/linhagem)
Where each number came from and what breaks if a table changes.
Data governance (/governanca)
Who sees what, and which personal data comes out masked.
Connect BI (/connect)
Excel, Power BI, Looker Studio, and Tableau reading your data.
Run your first query#
1. Find the table in the Explorer
On the left is the Explorer, with the datasets and tables. Use the "Search table…" search to filter. Click a table to select it.
2. Check the columns
With the table selected, View schema opens the columns and types (the panel also shows Rows, Size, Created, and Updated). Query table writes a ready-made
SELECTin the editor.3. See the cost first
Click Estimate: the screen shows how much the query will read and how much that costs — without running and without charging.
4. Run it
Click Run (shortcut
Ctrl+E; while running: "Running…"). The result appears below, in the Result tab.5. Save it, if you'll use it again
Give it a name in Query name and click Save. The query goes to the Saved tab.
What each button does#
| You want to | Click |
|---|---|
| Run the query | Run (shortcut Ctrl+E) |
| Know the cost first | Estimate |
| Save the query | Save (with the Query name next to it) |
| See a table's columns and types | View schema → Query table |
| Open another query without losing the current one | New query (opens a new tab) |
| Compare two queries side by side | Split (becomes Merge) |
| Create a dataset | Create dataset → Create |
| See personal data in clear text | Reveal PII (becomes Hide PII) |
| Take the result elsewhere | Export → Confirm and download CSV |
The bottom panel has three tabs: Result · History · Saved. In the Saved tab, Load in editor brings the query back. The result comes in pages (Previous · Next, and Rows per page).
Every run is billed
The amount depends on the volume of data the query reads, not on the number of rows returned. That's why Estimate exists: it's free. When the same query was run a short while ago, the result may come from the cache, marked as "⚡ cache · free".
When the SQL changes data#
The product asks for confirmation when the SQL changes or deletes data
Before running, the screen asks in no uncertain terms: "⚠ This CHANGES data — confirm?" or "⚠ This DELETES data — confirm?", and the confirmation button repeats the action: Confirm and CHANGE / Confirm and DELETE. There's no path where a write happens without this step — and it can't be undone.
Personal data (PII)#
By default, columns marked as personal data come masked: "PII data is anonymized in the query — only in our layer, without changing the datalake." Those with permission can click Reveal PII; the screen then warns "PII data REVEALED in this view — access logged in the audit trail." To go back, Hide PII.
Who can reveal is decided on the Data governance screen.
Export the result#
Export opens the Export data warning: "The customer is responsible for exported data. Make sure it is handled properly under the Brazilian General Data Protection Law (LGPD) and your internal policies." The file comes out as CSV when you click Confirm and download CSV.
A large result is a sample
If the query produces more rows than the grid loads, the screen marks the
result as Partial result: the totals on screen aren't the whole
result. Aggregate in the SQL itself (SUM, GROUP BY) to see the complete
number.
When the screen is empty#
- No tables: "No datasets yet. Create pipelines and transformations to populate the datalake." — the first step is a pipeline.
- No run: "Run a query to see the result."
- Empty history: "No runs yet. Run a query to start the history."
- Nothing saved: "No saved queries. Use “Save” to reuse queries."
In a demo environment, the demo badge appears: nothing is actually read from the datalake.
Back to the app#
- Console: Data → Console
Next task#
- Queries screen — a question in plain language becomes SQL
- Cost, limits, and security
- Medallion pipeline (Bronze, Silver, Gold)