The following tables list the required and optional properties of the DB Data Sink Insert component. Required properties are displayed in bold text.
Property |
Description |
---|---|
Interface |
Specify the method or driver you want to use to connect to the data source. |
Host Name |
Specify the data source. Options available on the Host Name list depend on the Interface you select. If you use SQLite as a Host, type the path and file name to the SQLite database file (For example, c:\mySQLite.db). If a database with the name you specify does not exist, SQLite will create one. |
Destination Table |
Click the Destination Table icon to select the destination table from a set of existing tables or enter the Destination Table manually. You can also create a new Destination table based on a component’s port structure. See “Adding a Destination table”. |
Property |
Description |
---|---|
User and Password |
Specify an authorized database user and a password to protect the database against unauthorized access. |
Insert Options |
Click the Insert Options icon to determine how attributes will be inserted. The Include columns specify which attributes will be inserted. The SQL expression overwrites the attribute value with the value of the expression at the time of execution. Specify an INSERT statement for each attribute that will overwrite
the incoming value of the selected attribute. An example of the
SQL INSERT value clause is: Records will be inserted with all the attributes selected in the Insert Options window. Select or unselect any of the attributes. You can specify values for attributes that will be inserted, thus overwriting the corresponding value of the incoming attribute. |
Truncate Table |
Select the option to remove all records from the destination table when initializing the transformation process. |
Write Block Size |
Specify the number of records to be written to the file or pipe in a single write operation. |
Pre-processing SQL |
Click the Pre-processing SQL icon to create a query that runs during component initialization. Queries can include one or more SQL statements. If you use multiple statements, separate them with a semicolon (;). |
Post-processing SQL |
Click the Post-processing SQL icon to create a query that runs after all components execute. Queries can include one or more SQL statements. If you use multiple statements, separate them with a semicolon (;). |
Opening Attribute Quote |
Specify a prefix for attribute names in SQL statements. |
Closing Attribute Quote |
Specify a postfix for attribute names in SQL statements. |
Database |
Select the database you want to use as data source. Additionally, you must select an appropriate interface, and in some cases, specify an appropriate user ID and password. |
Schema |
Identifies the schema/owner you want to use as data source. The objects displayed will be restricted accordingly and new tables will be created in that schema. |
Standardize Data Format |
Select the option to 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 with a ' |
IQ Lock Table in Exclusive Mode |
Select the option to 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. |
Database Options |
Click the Database Options icon to set options that override performance defaults and control the behavior of some transactions. |