EXPORT

Purpose

Use this command to transfer data from Exasol into external files or database systems.

Prerequisites

• In Exasol, you need to have the system privilege EXPORT, plus the corresponding privileges to read the table contents.
• In the target system, you need to have the privileges to insert rows or writing files. You also need the rights to replace or truncate the target.
• When using a connection, you need to either have the system privilege USE ANY CONNECTION or the connection is granted by the GRANT statement to the user or to one of the user roles. For more information, refer to the CREATE CONNECTION section in Access Control Using SQL(DCL).

Usage Notes

• The progress of the data transfer can be viewed using the system table EXA_USER_SESSIONS (column ACTIVITY) through a second connection screen.
• For additional information about ETL processes, refer to the ETL in Exasol section.
• If no other option is specified, the data is appended to the target.
• Only statements or views with ORDER BY clause on the top level are exported in sorted order (only in case of files).

The following table provides you with an overview of the different elements and their meaning in the EXPORT command: 

Element	Meaning
data_src	The source data can either be a table (as an identifier like MY_SCHEMA.MY_TABLE) or a query (like 'SELECT * FROM DUAL'). For tables, you can also specify the columns to be used.
dbms_dst	Defines the database destination whose connection data is specified in the connection_def. You can choose among an Exasol connection (EXA), a native connection to an Oracle database (ORA) or a JDBC connection to any database (JDBC). For the target, you can define either a table or a prepared statement (for example, an INSERT statement or a procedure call). In the latter case, the data is passed as input data to the prepared statement. Please note that you have to use schema-qualified table names. Within the statement, use question marks as placeholders for the parameter values, for example: INSERT INTO t VALUES (?, ?, ?). EXPORT (SELECT a,b,c FROM myschema.t) INTO JDBC AT postgres_conn STATEMENT 'insert into pgschema.t(a,b,c) values (?,?,?)'; When using the TABLE syntax (as opposed to STATEMENT), the table name identifier is treated similarly to Exasol tables. If your remote systems expect case-sensitive syntax, you must use quote marks to delimit the table names. Further options for the target: Option Description REPLACE Drops the target table before the export is started. TRUNCATE Deletes all rows of the target table before the export is started. TRUNCATE cannot be combined with REPLACE or CREATED BY. CREATED BY Defines a creation string which is used to create the table on the target system before the export is started. The CREATED BY string must contain a single SQL statement; multiple statements are not supported.
file_dst	Specifies the data file target. Remote Files:  FTP, FTPS, HTTP, and HTTPS servers are supported if connection data is defined through the connection_def. The following are some of the considerations while using remote data file source: Certificates are not verified for encrypted connections. In case of URLs starting with “ftps://”, the implicit encryption is used. In case of URLs starting with “ftp://”, Exasol encrypts the user name and password (explicit encryption), if the server supports this. If the server requires encryption, then the whole data transfer is done encrypted. For FTP and FTPS servers, only passive mode is supported. For HTTP and HTTPS servers only basic authentication is supported. For HTTP and HTTPS connections, HTTP query parameters can be specified by appending them to the file name. Example: FILE 'file.csv?op=OPEN&user.name=user' Local Files: You can also export to local files on your client system. For exporting local files, the JDBC driver opens an internal connection to the cluster and provides an HTTP or HTTPS (SECURE-Option) server. When specifying the SECURE option, the data is transferred encrypted, but also with slower performance. This functionality is only supported for EXAplus and the JDBC driver. It can not be used in prepared statements or within database scripts. If you want to process a local file by an explicit program, you can use the tool EXAjload, which is included in the JDBC driver package. Execute this program without parameters to get information about the usage. The target file can either be CSV or FBV files and will then comply respectively to the format specifications in the CSV Data Format or the Fixblock Data format (FBV). File names may only consist of ASCII characters. A BOM Byte Order Mark is not supported. Compressed files are recognized by their file extension. Supported extensions are .zip, .gz (gzip) and .bz2 (bzip2). When specifying multiple files, the actual data distribution depends on several factors. It is also possible that some files are completely empty. When the files are local, they are written into one file. Cloud Storage Service: You can export files to a cloud storage service. For more details, see cloud_connection_def.
script_dst	Specifies the UDF script to be used for a user-defined export. Optionally, you can define a connection or properties which will be forwarded to the script. The specified script will generate a SELECT statement internally that will be executed to do the actual export. The script has to implement a special callback function that receives the export specification (for example, parameters and connection information) and returns a SELECT statement. For more information, refer to User-defined EXPORT using UDFs section. connection_def Optional connection definition for being able to encapsulate connection information such as password. For more information, refer to the connection_def. WITH parameter=value... Optional parameters to be passed to the script. Each script can define the mandatory and optional parameters it supports. Parameters are simple key-value pairs, with the value being a string. For example: ... WITH PARAM_1='val1' PARAM_2 = 'val2';
connection_def	Defines the connection to the external database or file server. It can be specified within a connection string (for example, 'ftp://192.168.1.1/') and the corresponding login information. For regular ETL jobs, you can also make use of connections where the connection data like username and password can easily be encapsulated. For more information, refer to the CREATE CONNECTION statement in Access control using SQL (DCL) section. The declaration of user and password within the EXPORT command are optional. If they are omitted, the data of the connection string or the connection object are used.
cloud_connection_def	Defines a connection to a cloud storage service. This can be specified within a connection string and the corresponding authentication information. The connection string format may vary by cloud service. Example: EXPORT table1 INTO CSV AT CLOUD AZURE BLOBSTORAGE 'DefaultEndpointsProtocol=https;EndpointSuffix=core.windows.net' USER '<AccountName>' IDENTIFIED BY '<AccountKey>' FILE '<container>/<blob>'
csv_cols	Defines how the column data is written to the CSV file. For more information, refer to the CSV DATA Format section. col_nr Defines the column number starting from one. Alternatively, you can define a certain column range (for example, 5...8 for columns 5,6,7,8). Column numbers must be in ascending order. FORMAT Optional format definition for numbers or datetime values (default: session format). For more information, see Numeric Format Models and Date/Time Format Models. DELIMIT In the default case (AUTO), the field delimiters are written only if special characters occur within the data: the COLUMN SEPARATOR, the ROW SEPARATOR, the COLUMN DELIMITER, or a whitespace character. By using the options ALWAYS or NEVER you can define whether column separators shall always be written, or never. This local column option overwrites the global option. For more details, see file_opts. Using the NEVER option may have the result that the exported data cannot be imported again into Exasol. Example In this example, four columns are exported into the CSV file, and the column uses the data format specified for the CSV file. (1..3,4 FORMAT='DD-MM-YYYY')
fbv_cols	Defines how the column data is written to the FBV file. For more information, see Fixblock Data Format. The following elements can be specified in an FBV file: Elements Description SIZE Defines the number of bytes of the column. The default value is calculated by the source data type. Data Type Default Number of Bytes BOOL 1 DECIMAL(p) p+1(Sign) DECIMAL(p,s) p+2(Sign+Point) DECIMAL(p,p) p+3(Sign+Point+Leading zero) DOUBLE 21 DECIMAL/DOUBLE with format Dependent of format string DATE/TIMESTAMP Dependent of format string VARCHAR(n)/CHAR(n) n*4 in case of UTF-8 columns, n in case of ASCII columns. FORMAT Optional format definition for numbers or date time values (default: session format). For more information, refer to Numeric Format Models and Date/Time Format Models sections. ALIGN Alignment of the column (LEFT or RIGHT). The default value is LEFT. PADDING Padding characters for columns. By default, space is used. You can also specify an ASCII character, either in plain text ('+'), or as hexadecimal value ('0x09'), or as abbreviation('NUL', 'TAB', 'LF', 'CR', 'ESC'). Example In this example, four columns are exported into the FBV file. The first column is aligned to the right, and filled with 8 bytes with + characters, the fourth column has the specified data format. (SIZE=8 PADDING='+' ALIGN=RIGHT,  ,  ,  FORMAT='DD-MM-YYYY')
file_opts	REPLACE Replaces the target if it already exists. In case of HTTP[S] servers, the target file will always be newly created due to protocol limitations. TRUNCATE Deletes the data of the target before loading data. ENCODING Encoding of the CSV or FBV files (default is UTF-8). For information on the supported encodings, refer to Supported Encodings for ETL Processes section NULL Representation of NULL values. If you did not specify this option, NULL values are represented as the empty string. BOOLEAN Representation of boolean values. The following value pairs can be defined in a string: '1/0', 'TRUE/FALSE', 'true/false', 'True/False', 'T/F', 't/f', 'y/n', 'Y/N', 'yes/no', 'Yes/No', 'YES/NO' These pairs are automatically accepted when inserting strings into a boolean column using the IMPORT command. ROW SEPARATOR Line break character:  'LF'(Default): Corresponds to the ASCII character 0x0a (Unix) 'CR': Corresponds to the ASCII character 0x0d (Macintosh) 'CRLF': Corresponds to the ASCII characters 0x0d and 0x0a (Windows) 'NONE': No line break. This is only allowed in FBV files. COLUMN SEPARATOR Defines the field separator for CSV files. By default, the comma (,) is used. You can specify any string, either as plain text (','), as a hexadecimal value ('0x09'), or as an abbreviation (one of 'NUL', 'TAB', 'LF', 'CR', 'ESC'). A plain text value is limited to 10 characters, which will be automatically converted to the file's specified ENCODING. A hexadecimal value is limited to 10 bytes (not characters) and will not be converted. COLUMN DELIMITER Defines the field delimiter for CSV files. By default, the double quote (") isused. You can specify any string, either as plain text ('"'), as a hexadecimal value ('0x09'), or as an abbreviation ('NUL', 'TAB', 'LF', 'CR', 'ESC'). A plain text value is limited to 10 characters and will be automatically converted to the file's specified ENCODING. A hexadecimal value is limited to 10 bytes (not characters) and will not be converted. If you do not want to use any field delimiter, you can define the empty string (''), or use the option DELIMIT NEVER. DELIMIT In the default case (AUTO), the column delimiter is written only if special characters occur within the data: the COLUMN SEPARATOR, the ROW SEPARATOR, the COLUMN DELIMITER or a whitespace character. By using the options ALWAYS or NEVER you can define whether column separators should be written always or never. This global option can be overwritten within the single column definitions, refer to csv_cols for more information. Using the NEVER option may have the result that the exported data cannot be imported again into Exasol. WITH COLUMN NAMES With this option (only possible for CSV files) an additional row is written at the beginning of the file which contains the column names of the exported table. In case of a subselect, this can also be expressions. The other options, such as the column separator, are also applied for that row. If you want to import the same file again, use the IMPORT statement with option SKIP = 1.
error_clause	This clause defines how many invalid rows of the source are allowed. For example, in the case of REJECT LIMIT 5, the statement will work fine if there are less than or equal to five invalid rows and would throw an exception after the sixth row. REJECT LIMIT 0 has the same behavior when you have omitted the error clause completely.

Examples

EXPORT tab1 INTO CSV
       AT 'ftp://192.168.1.1/' USER 'agent_007' IDENTIFIED BY 'secret'
       FILE 'tab1.csv'
       COLUMN SEPARATOR = ';'
       ENCODING = 'Latin1'
       WITH COLUMN NAMES;

CREATE CONNECTION my_connection
       TO 'ftp://192.168.1.1/' USER 'agent_007' IDENTIFIED BY 'secret';

EXPORT (SELECT * FROM T WHERE id=3295) INTO FBV
       AT my_connection
       FILE 't1.fbv' FILE 't2.fbv'
       REPLACE;

EXPORT (SELECT * FROM my_view) INTO EXA
       AT '192.168.6.11..14:8563'
       USER 'my_user' IDENTIFIED BY 'my_secret'
       TABLE my_schema.my_table
       CREATED BY 'CREATE TABLE my_table(order_id INT, price DEC(18,2))';

EXPORT tab1 INTO JDBC DRIVER='MSSQL'
       AT 'jdbc:sqlserver://dbserver;databaseName=testdb'
       USER 'agent_007' IDENTIFIED BY 'secret'
       TABLE my_schema.tab1;

EXPORT tab1 INTO CSV
       AT 'http://HadoopNode:50070/webhdfs/v1/tmp'
       FILE 'file.csv?op=CREATE&user.name=user';

EXPORT tab1 INTO SCRIPT etl.export_hcat_table
WITH HCAT_DB = 'default'
     HCAT_TABLE = 'my_hcat_table'
     HCAT_ADDRESS = 'hcatalog-server:50111'
     HDFS_USER = 'hdfs';

EXPORT tab1 INTO LOCAL CSV FILE '/tmp/my_table.csv'
COLUMN SEPARATOR = ';';

Export data to an Amazon S3 bucket:

EXPORT tab1 INTO CSV
AT 'https://testbucket.s3.amazonaws.com'
USER '<AccessKeyID>' IDENTIFIED BY '<SecretAccessKey>'
FILE 'file.csv';

Export data to an Amazon S3 bucket with a fully qualified bucket URL:

EXPORT tab1 INTO CSV
AT 'https://testbucket.s3-<region>.amazonaws.com'
USER '<AccessKeyID>' IDENTIFIED BY '<SecretAccessKey>'
FILE 'file.csv';

EXPORT table1 INTO CSV AT CLOUD AZURE BLOBSTORAGE 'DefaultEndpointsProtocol=https;EndpointSuffix=core.windows.net' USER '<AccountName>' IDENTIFIED BY '<AccountKey>' FILE '<container>/<blob>'

Encryption for Exporting File to AWS

The EXPORT statement supports server-side encryption with Amazon S3-Managed Keys (SSE-S3) and with Customer Master Keys (CMKs) Stored in AWS Key Management Service (SSE-KMS). To know about the server side encryption options available with AWS, see Protecting Data Using Server-Side Encryption.

Exasol doesn't support Server-Side Encryption with Customer-Provided Keys (SSE-C).

To enable the encryption, you need to add the following parameters in IDENTIFIED BY field of your statement:

Examples

SSE-S3 encryption, user/password authentication:

EXPORT test_table INTO CSV AT 'https://testbucket.s3.amazonaws.com'
USER '<key-ID>' IDENTIFIED BY '<secret-key>;sse_type=AES256'
FILE 'testpath/test.csv';

SSE-KMS encryption with encryption context, temporary credentials for EC2 role authentication:

EXPORT test_table INTO CSV AT 'https://testbucket.s3.amazonaws.com'
USER '' IDENTIFIED BY ';sse_type=aws:kms;kms_key_id=arn:aws:kms:eu-west-1:<XXXXX>:key/<YYYYY>;enc_context={"foo":"bar", "baz":"qux"}'
FILE 'testpath/test.csv';