Back to Index

 

ODP.NET - Oracle Data Provider for .NET

ODP.NET is an object built specifically around the Oracle Data Provider for .NET classes.  It takes advantages of some very high-performance, Oracle specific features such as Array Binding to allow your VIS jobs to run as fast as possible against an Oracle database.

To use this data object, simply drag and drop it onto the designer window and dbl-click it (or press F4) to fill it the properties.  

Please note: We currently do not distribute the ODP.NET driver along with VIS.  If you wish to use this object, please download and install the ODP.NET data provider directly from Oracle's website at:  http://www.oracle.com/technology/tech/dotnet/index.html

See also: Setup requirements for ODP.NET

Properties

Action

Describes the action to take for output streams.  Ignored for input streams.  Valid options are:

Option

Description

None

Take no action

ClearThenInsert

Clears the table, then inserts records

InsertOnly

Inserts record into table

UpdateOnly

Updates record only where the specified key columns match

InsertOrUpdate

Attempts to update record where the specified key columns match, if no matching record is found the record is inserted into the table

DeleteOnKeyMatch

Deletes record only where the specified key columns match

ColumnLayout

The column layout (or file structure) of the table.  Click on the Ellipse (...) button to fill in the column layout, or select an existing column layout from the repository.  See also (Column level Write Flags)

CommandTimeout

Specify the maximum number of seconds to wait for any command that is sent to the database.  Once this time is exceeded you will receive a timeout error.

ConnectString

(read only) This property displays the ConnectString that will be used to connect to the data source.  It is built automatically by deriving the information from the other properties.

ConnectStringOtherParams

Any custom parameters to be included in the ConnectString. (example: see OleDb)

CreateTable

The create table property allows you to create your output table in the database during the job execution.  You can also choose to DROP the table prior to creating it.  The create table wizard will also generate your create table statement for you based on the pre-defined ColumnLayout.

DateTimeFormat

DateTime format mask to use when loading the data.  This is a useful way to format all columns defined as DateTime to standard format.  It saves you time from having to format each column individually in the Join object.  If the column is left blank the date will be read as it is received from the database.   Click on the ellipse to use the mask builder tool.

RowsPerTransaction

This data object supports batch SQL transactions which can greatly enhance the loading speed of a BlueSky Integration Studio job.  Simply enter the number of SQL statements to place in the internal queue before submitting them to the database.  For instance; by entering 1000 in this property, BlueSky Integration Studio will not attempt to send the data until 1000 records have been read from the input source, or until the last record is read (i.e. if there are only 300 input records, of course it will then write them to the database).   The database can process 1000 sql statements at once using Oracle's Array binding technology, much faster than 1000 individually sent sql statements.

Server

The server name where your database resides.  For Oracle you would enter the database SID.

Signon

The user name and password to use to connect to the database.  The password is hidden in this property.  Click the Ellipse (...) button on the property where you can enter both the user name and hidden password.

Tablename

Database table name

Comments

Comment area to give descriptive text about the data object and its purpose.

Alias

Alias identifier.  Aliases are used on all design objects to simplify coding and to ensure each object has a unique identifier.

Name

Descriptive name for this object.  You can enter any text to describe the object

GenerateSql

Yes / No.  By default, the data object will automatically generate the SQL Select statement for you deriving the information from other properties such as the Tablename and ColumnLayout properties.  By changing this property to No you can hand-code the SQL statement in the SQLSelect property window.  This gives you complete flexibility to enter SQL statements that join multiple tables together and/or use database optimizer hints.

OnPostDMLFailure

ContinueOn / AbortJob  : When DML (data manipulation language) statements are entered into the PostDML property, you can control whether your job continues executing if the DML statement fails for some reason.  DML statements include any valid UPDATE, INSERT or DELETE type of SQL statements. (see Pre / Post DML example)

OnPreDMLFailure

ContinueOn / AbortJob  : When DML (data manipulation language) statements are entered into the PreDML property, you can control whether your job continues executing if the DML statement fails for some reason.  DML statements include any valid UPDATE, INSERT or DELETE type of SQL statements. (see Pre / Post DML example)

PostDML

DML (data manipulation language) statement to execute after the job or Join object completes.  Any valid INSERT, UPDATE or DELETE type of SQL Statement. (see Pre / Post DML example)

PreDML

DML (data manipulation language) statement to execute before the job or Join object starts.  Any valid INSERT, UPDATE or DELETE type of SQL Statement. (see Pre / Post DML example)

PreLoadKeysIntoMemory

True or False.  This property is only used when using the UpdateOrInsertNew Action property.  By Pre-loading all of the output tables keys into memory, lookups can be performed much faster during the process of deciding whether or not the output object should Update an existing record, or insert a new record if the specified key value does not exist in the table.

Please note: You must put a little thought into this property.  Obviously, if your output table has 50 million records in it, you probably don't want to pre-load all the keys into memory as you will probably run out of memory in a hurry.  This feature is great for small to mid-sized table, like a Dimension in a data warehouse.  Your key size is also a factor, for instance; if you have a small, one column numeric key, you can fit a lot more records into memory.  If your key is multiple columns, try to determine the number of bytes of your total key columns and determine how many records you can fit into memory comfortably.  

SQLOutputFile

(output only).  This SQLOutputFile is the path and filename to a file where you want the actual SQL statements being generated to be logged.   This can come in handy when you are trying to debug a job, or some problematic data.  In production it is best to leave this property empty.  For instance: c:\jobsql.log

SQLSelect

The SQL Select statement that will be used for data objects used in input streams.  The SQL statement is built automatically by deriving information from other properties such as the Tablename and ColumnLayout properties.  You can override this SQL Statement by setting the GenerateSQL property to No.

 


© 2003 - 2007 Relational Solutions, Inc. - All rights reserved