Showing posts with label destination. Show all posts
Showing posts with label destination. Show all posts

Monday, March 26, 2012

Fetching an id to use in another task

Hi there,

i have a task that has a ole-db destination. it inserts some data to a table. it's always 1 record that is gonna be inserted.after that the task is finished. however i want to use that same record in the followup-task. is there a way to retrieve the id of that specific record.

Please note that the id of the record is an int-identity from sql-server itself.

at the moment i'm fiddling with "remembering" the inserted data and hopefully it will be a 100%match in the next task, but i have a dark feeling it's not 100%.

is there a common way how to approach this?

The simplest way I can see is to use a Execute SQL task in the control flow to retrieve it after the Dataflow that inserted the row is done.

sql

Monday, March 12, 2012

FastLoadMaxInsertCommitSize for Data Flow Destinations

Is there a way to programatically set (using expressions, variables) the FastLoadMaxInsertCommitSize property of an OLEDB destination in a data flow for Fast Load Operations.
Basically, what I want to do is based on the # of records which are going to be inserted want to set the FastLoadMaxInsertCommit size.

FastLoadMaxInsertCommitSize is not an expressionable property, so you can't use expressions, variables etc. to set it. Feel free to raise this as a request if you think it is really important for you.

FastLoad OLEDB Destination with Oralce

Hi,

why Table or View – fast load option in Data Access mode is not listed when we connect Oracle Database in the OLEDB Destination.

Thanks

Jegan

When you switch data sources using an OLE DB destination, you are most probably using a different kind and version of the OLE DB provider. I'm guessing that in your case, you are using Microsoft's Oracle OLE DB provider? that `-fast load` option is a feature of the underlying OLE DB Provider, which in your case, I'm guessing is Microsoft's OLE DB provider (SQL Native Client). And that is probably not a feature of the underlying OLE DB Provider for Oracle that you are using, and thus, do not show-up as an option.

|||Thanks Deniz.