Early Access: The content on this website is provided for informational purposes only in connection with pre-General Availability Qlik Products.
All content is subject to change and is provided without warranty.
Skip to main content

Store

The Store statement creates a QVD, Parquet, or text file.

Syntax:  

Store [ fieldlist from] table into filename [ format-spec ];

The statement will create an explicitly named QVD, Parquet, or text file.

The statement can only export fields from one data table. If fields from several tables are to be exported, an explicit join must be made previously in the script to create the data table that should be exported.

The text values are exported to the CSV file in UTF-8 format. A delimiter can be specified, see LOAD. The store statement to a CSV file does not support BIFF export.

You can specify whether to store your file in your personal space or a shared space where you have write permissions. If you store in a shared space, members can use that data to create apps in the space. See: Managing permissions in shared spaces.

Arguments:  

Store command arguments
Argument Description
fieldlist::= ( * | field) { , field } )

A list of the fields to be selected. Using * as field list indicates all fields. 

field::= fieldname [as aliasname ]

fieldname is a text that is identical to a field name in table. (Note that the field name must be enclosed b straight double quotation marks or square brackets if it contains spaces or other non-standard characters.)

aliasname is an alternate name for the field to be used in the resulting QVD or CSV file.

table A script label representing an already loaded table to be used as source for data.
filename

The name of the target file including a valid path to an existing folder data connection.

Example:  

  • Personal space: [lib://DataFiles/xyz.qvd]

    '/' delimited path hierarchies can be used in file names. However, the Data Load Editor and Data Manager UIs do not currently support displaying paths in a hierarchical manner. If a '/' delimited file name is used, it will appear in its entirety in the filename column.

  • Shared space: [lib://TeamSharedSpace:DataFiles/xyz.qvd]
format-spec ::=( ( txt | qvd | parquet), compression is codec)

You can set the format specification to either of these file formats. If the format specification is omitted, qvd is assumed.

  • txt for text files.

  • qvd for QVD files.

  • parquet for Parquet files.

If you use parquet, you can also set which compression codec to use with compression is. If you do not specify the compression codec with compression is, snappy is used. The following compression settings are available:

  • uncompressed

  • snappy

  • gzip

  • lz4

  • brotli

  • zstd

  • lz4_hadoop

Example:

Store mytable into [lib://DataFiles/myfile.parquet] (parquet, compression is lz4);

Information noteThe file extension of DataFiles connections is case sensitive. For example: .qvd.

Examples:  

Store mytable into [lib://DataFiles/xyz.qvd];

Store * from mytable into [lib://DataFiles/myfile.qvd];

Store Name, RegNo from mytable into [lib://DataFiles/xyz.qvd];

Store Name as a, RegNo as b from mytable into [lib://DataFiles/myfile.qvd];

Store mytable into [lib://DataFiles/myfile.txt] (txt);

Store mytable into [lib://DataFiles/myfile.parquet] (parquet);

Store * from mytable into [lib://DataFiles/myfile.csv] (txt);

Store * from mytable into [lib://TeamSharedSpace:DataFiles/myfile.qvd];

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!