# Parameters for the export procedures

The Derby export procedures use specific parameters.

`SCHEMANAME`
  Specifies the schema of the table. You can specify a NULL value to use the default schema name. The `SCHEMANAME` parameter takes an input argument that is a VARCHAR(128) data type.
`SELECTSTATEMENT`
  Specifies the SELECT statement query that returns the data to be exported. Specifying a NULL value will result in an error. The `SELECTSTATEMENT` parameter takes an input argument that is a VARCHAR(32672) data type.
`TABLENAME`
  Specifies the table name of the table or view from which the data is to be exported. This table cannot be a system table or a declared temporary table. The string must exactly match the case of the table name. Specifying a NULL value results in an error. The `TABLENAME` parameter takes an input argument that is a VARCHAR(128) data type.
`FILENAME`
  Specifies the file to which the data is to be exported. If the path is omitted, the current working directory is used. If the name of a file that already exists is specified, the export utility overwrites the contents of the file; it does not append the information. The specified location of the file should refer to the server-side location if you are using the Network Server. Specifying a NULL value results in an error. The `FILENAME` parameter takes an input argument that is a VARCHAR(32672) data type.
`COLUMNDELIMITER`
  Specifies a column delimiter. The specified character is used in place of a comma to signify the end of a column. You can specify a NULL value to use the default value of a comma. The `COLUMNDELIMITER` parameter must be a CHAR(1) data type.
`CHARACTERDELIMITER`
  Specifies a character delimiter. The specified character is used in place of double quotation marks to enclose a character string. You can specify a NULL value to use the default value of a double quotation mark. The `CHARACTERDELIMITER` parameter takes an input argument that is a CHAR(1) data type.
`CODESET`
  Specifies the code set of the data in the export file. The code set name should be one of the Java supported character encoding sets. Data is converted from the database code page to the specified code page before writing to the file. You can specify a NULL value to write the data in the same code page as the JVM in which it is being executed. The `CODESET` parameter takes an input argument that is a VARCHAR(128) data type.
`LOBSFILENAME`
  Specifies the file that the large object data is exported to. If the path is omitted, the LOB file is created in the same directory as the main export file. If you specify the name of an existing file, the export utility overwrites the contents of the file. The data is not appended to the file. If you are using the Network Server, the file should be in a server-side location. Specifying a NULL value results in an error. The `LOBSFILENAME` parameter takes an input argument that is a VARCHAR(32672) data type.

If you create a schema, table, or column name as a non-delimited identifier, you must pass the name to the export procedure using all uppercase characters. If you created a schema or table name as a delimited identifier, you must pass the name to the export procedure using the same case that was used when it was created.

Parent topic: Exporting data using the built-in procedures
Related tasks
Exporting data using the built-in procedures