Friday, February 24, 2012

issue oledb

I use oledb to insert the data to respective tables..

then i have a look up where i check for unique field of the data i inserted which shows up with an error No matter what i do...

It will help us help you if you post that error.|||

Here is the error

[Lookup 3 [39523]] Error: Row yielded no match during lookup.

[Lookup 3 [39523]] Error: The "component "Lookup 3" (39523)" failed because error code 0xC020901E occurred, and the error row disposition on "output "Lookup Output" (39525)" specifies failure on error. An error occurred on the specified object of the specified component.

[DTS.Pipeline] Error: The ProcessInput method on component "Lookup 3" (39523) failed with error code 0xC0209029. The identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running.

[DTS.Pipeline] Error: Thread "WorkThread0" has exited with error code 0xC0209029.

this is what i do..and shows the about error mentioned above..

After inserting using oledb command in the lookup i look up for two columns and then get respective key field to that columns and then i insert it to other table using oledb

|||

The Lookup component treats the no matches as errors; that is what you are seeing. Are you expecting to have a match for every row that pass trhough the Lup component?

if so; make sure the mapping inside of the lookup is right and the table/query that supports it has all the expected values.

If not; configure the error output of the component to either redirect or ignored the no matches.

|||

yes i am looking to see if there is a match using lookup.There should be a match as i am inserting the records just before having a lookup...But the lookup shows error(red). i have been looking for data in the table and the lookup which i am pointing to...they dont have any problem...one possible reson might be the lookup is running even before respective record is been inserted as oledb command is slow and lookup is fast..

|||

With the default settings, the lookup will cache all of the data as soon as the dataflow begins. If you are inserting the records in the dataflow, the lookup will not have them in cache. You can avoid this by going to the Advanced tab in the lookup editor and selecting Enable Memory Restriction. This will have an impact on performance, as now the lookup will query the database for each row passing through it.

If you have a lot of repeated values that you are trying to look up, you could play with the Enable caching options to see if you can get decent performance. With this option set, it doesn't cache anything at the start, but rows are cached as they are looked up from the source. If it doesn't find the row in cache, it will check the database.

|||thank You for your prompt reply.....this seem to work now....I have one more question for you...i use oledb as i transform incoming data to multiple tables at a time....which is very slow.....what would be the best solution for fast performance? if script component how do i need to do it please let me know how to use this or any links would help..|||

Please mark the answers that were helpful.

Have you looked at using a multicast with several OLEDB destinations?

|||No i havent used....when i connected oledb output to multicast is didnt show up with incoming columns..|||I just want to increase the performance since oledb is slow...|||

sureshv wrote:

No i havent used....when i connected oledb output to multicast is didnt show up with incoming columns..

You should have a source component connected to the multicast. You can then drag multiple outputs from the multicast to your destinations (OLEDB Destinations, not OLEDB Commands).

|||hey is there a way to enter some of the incoming data into one table and get the key to it and then insert the rest of the data along with the key into another table...I do it using oledb command which works...but is there any other way i can implement it which is faster...

No comments:

Post a Comment