The following fields are available to define the location, name and contents of the exported data file:
SQL Server File Attributes example screen:
Greenplum File Attributes example screen:
Fields | Description |
---|---|
Export Type | Method of exporting data from the table. The available options are dependent on the Destination connection that can be specified via the Properties page. |
Destination Connection | Destination to the file system to which data will be exported. The destination connection can be specified on the Properties screen. |
Export File Definition
Fields | Description |
---|---|
Export File Path | The full path (absolute path) of the folder/directory where the File is to be created on the Windows or UNIX/Linux system. |
Export File Name | Name of the Export File to which the data will be exported. The variable $SEQUENCE$ can be used to provide a unique sequence number for the export file. Also, the data/file components YYYY, MM, HH, MI, SS can be used when enclosed with the $ character. For example, an export file name might be budget_$YYYYMMDD$.txt which would result in a file name like budget_20150520.txt. |
Export Routine | Database-specific routine to use to export the data. In SQL Server this is BCP or isql. In later versions of SQL Server this is BCP or sqlcmd. For Oracle this is SQL*Plus. For DB2 the supported export routine is EXPORT. For Greenplum, the supported export routine is COPY. For PDW, the supported export routine is sqlcmd. |
Use Temp Table | This option is only available for Greenplum and is enabled by default. Ticking this checkbox creates a temporary table to export the data into. The temporary table is then deleted once the data has been exported. |
Export Format | Routine-specific format to use to export the data. This is the format of the data in the export file and is either Delimited Text or Width Fixed Text in Oracle and SQL Server. In DB2, the supported formats are DEL (delimited), WSF (worksheet format) and IXF(intergrated exchange format). In Greenplum, the supported formats are Text and CSV. |
Export File Delimiter | Character that separates the fields within each record of the Export File for Delimited formats. The delimiter identifies the end of which field. Common field delimiters are tab, comma, colon, semi-colon, pipe. To enter a special character, enter the uppercase string CHAR with the ASCII value in brackets (e.g. CHAR(9) ). This is only available if the Export Format is Delimited Text. |
Optionally Enclosed by | Character that brackets text fields within each record of the Export File for Delimited formats. A common example is ". This is only available if the Export Format is Delimited Text. |
Header Row in Export | If a header line is required, choose business names or column names from this drop-down list. This option is not available in DB2. |
Export Options | Allows the entry of export utility options. If more than one option is required, then a semi-colon should be used between options. This option is not available in DB2. |
Export Modifier | DB2 only. This allows the entry of EXPORT modifiers in DB2. |
Trigger File
Fields | Description |
---|---|
Trigger file | If a trigger file is specified, then this file is created after the export file. It will normally contain a row count and a check sum. |
Trigger Path | The purpose of the trigger file is to indicate that the export to the main file has completed and that it is now safe to load the file. Secondly the trigger file may contain control sums to validate the contents of the main load file. This field should contain the full path name to the directory in which a trigger file is to be generated on the destination system. |
Trigger Name | Refers to the name of the file that is to be created as a trigger file. A trigger file typically contains check sums (row count or the sum of a numeric column). The variable $SEQUENCE$ can be used to provide a unique sequence number for the trigger file. Also, the data/file components YYYY, MM, HH, MI, SS can be used when enclosed with the $ character. For example, a trigger file name might be budget_$YYYYMMDD$.txt which would result in a file name like budget_20150520.txt. |
Trigger Delimiter | Multiple fields in the trigger file are to be separated by the trigger delimiter. |
Trigger Parameter 1,2,3 | The checksums to be put in the trigger file. One of the row count and the sum of any numeric fields in the source data. Compress After Export Check this box if you want to compress the export file after it has been created. Compress Utility Path The directory in which the compress utility exists. Compress Utility Name The name of the compression utility executable. Compress Parameters The name of the file to be compressed (using the WhereScape RED variable $EXPFILE$) and any commands or switches required to make the compression utility work. These parameters will depend on the compression utility used. |
File Actions
Fields | Description |
---|---|
File Action 1, 2, 3 | File Actions are only available for Greenplum. Use these fields to enter any command lines to run after the export such as copying files to another machine or deleting files. |