Gnok is in Limited Availability: a preview with no uptime commitment. Don’t store sensitive data; data may be deleted.
Skip to main content

Exporting your data

Gnok is in Limited Availability: data stored during the preview may be deleted. Keep a copy of anything you need.

Query results and tables​

  1. In Studio's SQL editor, run a query for the data you want, for example:

    SELECT * FROM my_catalog.my_schema.orders;
  2. In the results toolbar, open the download menu and choose Download CSV or Download JSON.

Studio loads up to 10,000 rows into the browser. When a result has more rows, the menu also offers Export all as CSV and Export all as JSON: Gnok runs the query again on the server with no row limit and streams the whole result to a file.

To download a whole table as one file, open it in the Data browser and choose Download → CSV or Download → Parquet, or use Download as CSV / Download as Parquet in the table's menu in the tree.

During the trial a query can run for at most 5 minutes, and that includes an export. Export a large table in parts, for example by date range:

SELECT * FROM my_catalog.my_schema.orders
WHERE order_date >= DATE '2026-01-01' AND order_date < DATE '2026-04-01';

Worksheets, notebooks and dashboards​

  • Worksheets: copy the SQL from the editor into a file of your own.
  • Notebooks: copy the code from each cell. Downloading a whole notebook as a file isn't available yet.
  • Dashboards: Export JSON in a dashboard's menu saves its definition (layout, widgets and their queries). Each widget's data can be downloaded as CSV from the widget's menu.

Exporting with your own tools​

If your workspace has client access (email support@gnok.com to request it), you can export with a SQL client over the Postgres wire protocol:

COPY (SELECT * FROM my_catalog.my_schema.orders) TO STDOUT WITH CSV HEADER;

See Postgres wire protocol for connection details.

COPY … TO a file or to @stage and UNLOAD don't write files yet, and files uploaded to @stage can't be downloaded back, so export through query results or table downloads as above. (After your trial or subscription ends, Export all tables on Usage & billing writes Parquet or CSV files to your stage for you and gives you download links; see below.) The Python SDK and Flight SQL return results as Apache Arrow, which you can write to Parquet; see Python SDK.

Need help?​

For a full export of a large workspace, email support@gnok.com before you plan to leave or before the preview ends.

After your trial or subscription ends​

When your trial ends (its credits are used up or its 60 days pass) or your subscription ends, compute stops, but export doesn't. Until your data's retention ends (30 days after the trial's end date, or after the subscription's end), you can export it at no charge, without upgrading:

  • Usage & billing in Studio shows Export your data, with the date until which export is available and today's compute allowance for exports.
  • Exports run read-only on your workspace's default warehouse (compute_wh), which resumes for them. Other warehouses stay suspended.
  • The allowance is 2 CU a day (about 2 hours of the X-Small compute_wh), reset at 00:00 UTC. The compute is metered but not billed. When the day's allowance is used up, exports pause until the next reset, and Studio says when.

What you can do:

  1. Query it. Run SELECT statements in the SQL editor and download the results as CSV or JSON, as above.
  2. Download a table as CSV or Parquet from the Data browser.
  3. Export all tables. On Usage & billing, choose the format (Parquet or CSV) and start Export all tables. A background job writes every base table (views aren't included) to your workspace's stage and lists download links there as it goes.

Statements that change data (INSERT, UPDATE, DELETE, MERGE, DDL), loads (COPY INTO <table>), notebooks and AI requests stay refused until you upgrade or subscribe again; notebooks open read-only. When the 30 days pass, the workspace is deleted as described in Deleting your workspace.