Convert ZST to SQL

Turn ZST archives into SQL. The Zstandard layer is removed and the bytes inside are written as they were.

Converted in an isolated sandbox on our serversDeleted after 24 hours

Drop ZST files on the dialor turn it to pick what to do

A SQL script with the compression removed.The Zstandard layer comes off. The SQL inside is written out as it was.

  1. What you get

    One SQL file. The conversion removes the Zstandard layer and writes the bytes inside exactly as they were, so the statements are the same ones that went in.

    The result is a script that any SQL tool can read or replay.

  2. What it expects

    Ask for the format you know is inside the ZST file. If the contents are not SQL, the request is refused. The conversion does not turn one kind of content into another.

    There are no options to set. The conversion takes the file and returns the one SQL file.

  3. When a conversion stops

    A file that cannot be parsed as Zstandard stops with input_corrupted.

    A file stops with unsupported_elements when it holds something the target cannot carry, or when an input cannot become the format the join takes.

  4. Going the other way

    To compress a script again, use SQL to ZST. Other conversions that start from ZST are listed under every ZST conversion.

ZST and SQL.What each format is.

The formats

From · ZST

Zstandard

A single file compressed with Zstandard, fast to compress and to decompress.

Extensions
.zst
MIME type
application/zstd
Kind
Archives
To · SQL

SQL Script

SQL statements as text. A database dump that any SQL tool can read or replay.

Extensions
.sql
MIME type
application/sql
Kind
Text and data

In your code.The same ZST to SQL conversion through the API, for your app or your agent.

terminal
$ cv convert archive.zst archive.sql
$ cv convert archive.zst archive.sql

Questions.What people ask about ZST to SQL.

01OF 04

No. The Zstandard layer is removed and the bytes inside are written as they were.

The request is refused. Ask for the format you know is inside the file.

No. This conversion has no options.

The file could not be parsed. The conversion stops with input_corrupted in that case.

More conversions.Other ways in and out of ZST and SQL.