DB Alias Tab for Sybase ASE

Use the DB Alias tab to define the parameters needed for theSybase ASE loader. The availability of certain options and fields might be dependent upon your entries for related options and fields on the tab.

Load Request Editor with DB alias for Sybase as the active tab. The elements are described in the following text.

Mode

Insert
Insert rows from the source file into the target tables. If the primary key values match, duplicate rows are discarded or inserted into the error file (if specified).
Replace
Clear and replace all existing rows in the destination tables with the rows from the source file.

Options

Perform Load
Run the loader automatically after file conversion is complete. If you clear this check box, the load process prepares the data in the appropriate format and creates a BAT file, but does not initiate the loader. You must ensure that the target tables are empty and edit the BAT file to include the appropriate password information before running. Sybase ASE does not accept a Replace operand for a load request.
Delete files if Successful
Fast load confirmation is not available. Delete the data files after the loader completes successfully.
Delete files if Failure
Fast load confirmation is not available. Delete the data files if the loader does not complete successfully.
Load When Source is Empty
Complete the load if a table to be loaded contains no rows, deleting any rows from the target. If not selected, empty source tables are skipped.

Disable Triggers

Use these options to disable triggers:

Always
Disable all database triggers for the load, re-enabling the triggers when the process completes.
Never
Execute all database triggers during the load.
Prompt
Selectively disable database triggers during the load and selectively re‑enable triggers when the process completes.

Error File Options

Create
Create a discard file.
Max Errors
The number of rows (up to 999999999) that the loader can discard because of errors. Stop processing when the specified number of rows is discarded.
  • To end the process if a single row is discarded, specify 1 as the maximum.
  • To allow an unlimited number of rows to be discarded, specify zero (0) or leave blank.

Additional Loader Parameters

You can augment the loader arguments created automatically with additional loader parameters. The parameters you create are appended to the list created automatically, but are not validated before starting the loader. For valid operands, see the database loader documentation. If additional loader parameters are forced from within product options, you cannot modify them.

Disable Constraints

Never
Never disable referential integrity constraints for the loader. This option causes a warning message when you run the loader.
Constraint Non-Disablement Warning dialog that is displayed if referential integrity constraints are not disabled.
Always
Disable constraints during the load process and re-enable constraints when the process is completed.
Prompt
Display the Disabling Trigger/Constraint Confirmation dialog to list tables with associated constraints. Right-click the Status During Process column to enable or disable the corresponding trigger or constraint during the load. Right-click the Status After Process column to enable or disable the corresponding trigger or constraint after the load completes.

Work path for interim files

Default directory path for temporary loader files.

Table Partition Mapping

If you want to store data in a specific partition, you must pass the partition name when you run the load. Use the Table Partition Mapping dialog to map the target or destination table to a partition. Use Tools > Edit Partition Map to open the dialog.

Table Partition Mapping dialog

The Table Partition Mapping dialog includes a tab for each Sybase DB alias referenced by the load request. Destination Table lists every table mapped by the table map. Use Partition to identify the partition for each table. Only one partition can be specified for a table. If the table contains data for other partitions, the loader generates an error. See the following example in which a table called “my_publishers” is partitioned, according to the values in the state column:

create table my_publishers
 (pub_id char(4) not null,
  pub_name varchar(40) null,
  city varchar(20) null,
  state char(2) null)
 partition by list (state)
(west values ('CA', 'OR', 'WA') on seg1,
 east values ('NY', 'MA') on seg2)

If the file contains data for California (CA), Oregon (OR), and Washington (WA), west is the partition. Conversely, if the file contains data for New York (NY) and Massachusetts (MA), east is the Partition.



Feedback