A custom table is a Lake table that your own SQL query defines. This page covers the popup that creates one: where the table lives, how the query is checked and what happens when you press Create. For the wider import journey, see Import tables.
Select a database, Select a schema and Enter table name.Write the query in the SQL Query editor. While the box has text, a chip beside Run Query shows where the check stands:
| Chip | What it means |
|---|---|
| Query not validated | The query has not passed a check, or it has changed since the last pass. |
| Query validated | The query passed the check. |
The check is tied to one database and one query text. Change either and the chip drops back to Query not validated, unless the database and the query exactly match what you last checked.
Run Query only checks the query; the table is created when you press Create. Cancel closes the popup without creating anything. If you have unsaved changes, the popup's Close button asks you to confirm first: "You have unsaved changes. Do you want to close the popup?" The popup keeps what you filled in through a page refresh.
The button needs more than a query: Database, Schema and Table Name must be filled in too. It is also inactive while a check runs and after the query has passed. Fill in the three fields; after a pass, edit the query to check a new version.
The check holds one database and one query text. The chip reads Query validated only while the current database and query are exactly the pair that last passed; any other change returns it to Query not validated, and Run Query restores it.
No. A database or schema that the popup was opened from arrives filled in and locked. If you need different values, close the popup and open it again from a level where the choice is free, such as the datasource row.
No. Run Query only checks the query and shows the result in the Query Data Preview window when it passes. The table is created only when you press Create.
On success the popup closes and the new table opens in its own popup, so you can set up its columns, sync and deployment right away.
Read the notification's description: it carries the reason from the server. The popup stays open with everything as you left it, so fix what the message points at and press Create again.
No. This popup does not check the chosen schema for an existing name while you fill the form, so pick a name that is unique in the schema. If the creation is refused, the Error notification carries the server's reason.
Because it holds something that has not been created yet: a name, a query, or a location that differs from what the popup opened with. Close in the confirmation closes the popup without creating the table; dismiss it to keep editing.