The following tables list the required and optional properties of the DB Data Sink Delete component.
Property |
Description |
---|---|
Interface |
Identify the method or driver you want to use to connect to the data source. |
Host Name |
Identify the data source. The options that appear on the Host Name list depend on the interface you select. |
Destination Table |
Select the destination table from a set of existing tables. You can also create a new Destination table based on a component’s port structure. See “Adding a Destination table” for more information. |
Key |
Select the columns of the destination table that identify the records to delete. You must select a Destination table before you can select a key. You can select multiple key columns. |
Property |
Description |
---|---|
User and Password |
Identify an authorized database user, and protect the database against unauthorized access. |
Shared Connection |
Select this option to allow the component to share a single connection to the database with other target components that have identical connection and database parameters. A connection can be shared only between components within the same project. Components in different projects within the same job cannot share a connection Components that use the same database interface and login information, but have differing database options cannot share a connection, and generate an error when the project is executed or simulated. |
Write Block Size |
Specify the number of records to be written to the file in a single write operation. |
Pre Processing SQL |
Create a script that runs during component initialization. Scripts can include one or more SQL statements. If you use multiple statements, separate them with a semicolon (;). |
Post Processing SQL |
Create a script that runs after all components execute. Scripts can include one or more SQL statements. If you use multiple statements, separate them with a semicolon (;). |
Opening Attribute Quote |
Prefix for attribute names in SQL statements. |
Closing Attribute Quote |
Postfix for attribute names in SQL statements. |
Database |
Identify the database to use as data source. If you select this option, you must also select an appropriate interface, and in some cases, specify an appropriate user ID and password. |
Schema |
Identify the schema/owner you want to use as data source. The objects that appear are restricted accordingly and new tables are created in that schema. |
Standardize Data Format |
Convert incoming Dates are converted into a format that includes the year,
month, day, hour, minute, seconds, and fraction of a second: For example: 2005-12-01 16:40:59.123 Numbers are converted using a period (“ |
IQ Lock Table in Exclusive Mode |
Lock the target table and prevent it from being updated by concurrent transactions. When an exclusive table lock is applied, no other transaction can execute queries or perform any updates against the locked table. The IQ Lock Table in Exclusive Mode option also queues multiple projects that load the same table in Sybase IQ. |
Wait Time for IQ Lock Table |
Specify the maximum blocking time that the project should wait before acquiring an Exclusive lock. Specify the time argument in the format hh:nn:ss.sss. If you do not enter a time argument, the server waits indefinitely until an Exclusive lock is available or an interruption occurs. When you specify “00:00:00.000” as the time argument, an Exclusive lock is acquired as soon as the project starts. |
Load Stage Path |
Specify a data file path. The load stage file must reside on the same machine as the IQ Server. When using a Sybase IQ database, if you specify a Load Stage Path, the component uses the LOAD TABLE statement instead of using SQL statements. This leads to faster performance. You do not have to enter the Load Stage Path if client side load balancing capability is available on your IQ Server. If available, it is automatically used with the LOAD TABLE statement to add records from files located on remote host machines into the Sybase IQ table. To create a pipe, specify pipe:// as the Load Stage parameter. A pipe is not used if the Load Stage is blank. If you use named pipes on UNIX or Linux, the ETL Server and the IQ Server must reside on the same machine. This is not a requirement for Windows. |
Load Stage (Server) |
Specify the server path to the data file or, leave it empty when using a pipe. If the Sybase IQ server needs to use a different path to the temporary data file than specified in the Load Stage property, enter it here. |
Database Options |
Set options that override performance defaults and control the behavior of some transactions. |
Transactional |
All work performed by the DB Data Sink Delete component, including pre-SQL and post-SQL, is done in a single database transaction that is committed when the project finishes normally. Select this option to roll back the transaction, if this component encounters an error. See “Job components” and “Enabling transactionality for projects and jobs” for information on the “Propagate Rollback” property. |