This page is used to define ODBC to SQL Server Export Specifications, which are used to extract data from files using an ODBC connection to Microsoft SQL server. Note: if you exporting data from U2 to SQL Server, use the U2 to SQL Export Specification to define your exports.
An ODBC Export Specification has two parts: selection and export. The selection portion of an export allows you to specify any selection criteria to apply to the data before the data export file is created. The export portion lists the fields to be included in the data export file, the column headings to use, and any data conversion required.
An export is normally processed in a Service using the command KMK.EXPORT.
|
|
Click the New icon in the toolbar to save the current export specification and then clear the page making it ready for a new item. |
|
|
Click the Save icon in the toolbar to save the current export specification and return to the export specifications listing. |
|
|
Click the Save As icon in the toolbar to save the current export specification to a new name. You will be prompted to enter a new name. Click OK to save the export to a new name and then continue editing the export. Click Cancel to return to the existing export without saving. |
|
|
Click the Delete icon in the toolbar to delete the current export specification. You will be prompted with a "Are you sure you want to delete?" dialog. Clicking Yes will permanently delete the export and then return to the export specifications listing. Click Cancel to return to the existing export without deleting. |
|
|
Click the Test icon in the toolbar to test an
export. Testing an export will perform a sample data extract using all
of the information entered on the export specification and then outputs
the results to the screen where it can be viewed and validated.
Typically a test is performed to ensure that the correct data fields are
being extracted and all data conversions, formats, and formulas are
working correctly. After clicking the Test icon, you will see a dialog requesting additional information:
Click the OK button to view the export results or click the Cancel button to return to the Export Specification page. Note: For this feature to work correctly you will need to: 1) Add the Kourier website as a trusted site so pop-up dialogs appear and 2) enable the automatic prompting for downloads option in your browser's internet options (e.g. for IE9 this setting is found in Security | Custom Level dialog). |
|
|
To see the runtime statistics for an individual export, click the Statistics icon from the toolbar. This will take you to the Export Statistics listing which displays all export statistics that have been captured for the export. |
|
|
To create the DDL from a SQL export specification, you may click the DDL button from the tool bar. Once the DDL has been created a dialog appears allowing you to view the DDL. This feature is useful when you need to only create the DDL for an single export instead of all of the exports associated with a master file. |
|
|
To create the SSIS Package from a SQL Export Specification, you may click the Generate Package button from the tool bar. Note, your current SQL Export Specification will be saved before you can create the SSIS package. This will open a new Generate SSIS Package page where you will be asked to enter a number of parameters before the SSIS package can be generated. |
|
|
Click the Help balloon to open the help for this page. |
KT_EXPORTS/Export Name
If an export contains user-defined literals, they should be entered using Substitution Literals.
None
| Field Name | Description - Usage - Notes | ||||||
| Name | Enter a unique name for the export. By convention, exports are named using an Integration ID such as KS for KommerceServer, followed by an underscore and a string that describes its purpose (e.g., KS_CONTACTS). | ||||||
| Title | Enter a short descriptive name for this export. This name is displayed in on-line lookups. | ||||||
| Export Format |
Enter the export format. If the export verb is KEXPORT, the possible
choices are shown below. Other export verbs (normally user-written
BASIC programs) may or may not support these formats.
|
||||||
| Last Update | Display only field, shows the last date/time that the export specification was saved. | ||||||
| Note | Enter a free form comment or note for this Export Specification. If a note is entered, a small icon will display on the Export Specification listing. Hovering your mouse over the icon on that listing will display about 40 characters of the note for quick reference. | ||||||
| Last Package Generation | Display only field, shows the last date/time that the associated SSIS package was successfully generated for this export specification. | ||||||
| ODBC Connection |
Select an ODBC Connection from the list of available choices to indicate what type of database will be used for the ODBC connection. For example: Oracle 11g, MS Access, MS SQL. These must be defined using the ODBC Connection page. |
||||||
| Source Table |
Enter a valid verb to perform the selection, such as SELECT or SSELECT. The export processor first processes the selection portion of the screen, and then passes the selected items to the export section. The selection portion of the screen can be used to limit the number of records exported. |
||||||
| SQL Table | Enter the name the SQL Server table to be used as the destination of the exported data. This name will be used in any DDL that is generated and when generating SSIS packages for this export. | ||||||
| Where |
Enter the selection criteria statement using the query syntax that is native to the source ODBC database. This is used to limit the data selected from theSoure table. This field may also contain substitution tags. |
||||||
| Net Change Where | Enter any addtional selection criteria using the query syntax that is native to the source ODBC database to provide additional data filtering before processing the file | ||||||
| Export Options |
Enter any valid export options.
|
Click the Add button in the line item section command bar to add a new line item field. See help for File to SQL Export Specification Line Item