DSXchange

Please first of all check whether you are using correct columns for the lookup then check the datatypes both from table and lookup.

Are you able to solve your problem.

can you give us some more details of your job so that we can analyse the problem

As your file is a piped delimited file you will be knowing the number of pipes (delimiters) per record. That is; you might know the number of columns present in the record.You can use an Index function to check the number of delimiters here. Check whether you can use for pipe symbol. Index function ...

Many thanks for your guidence Arnd.

My initial impression was that the indices of the two tables also same as the two tables are of same type.
I had look at the two tables and found the indices different for the tables.
This is the reason why i got the difference.
Thank for your valuble pointers.

Total number of records are more in table1 ( used in job1) than table2 ( used in job2).

I am having two extract jobs which are having same design and options. But I find a huge difference from performance point of view for both jobs. Job design is as follows: DB2database ------> Hashfile (Use account name has enabled) Job1 SQL: SELECT LTRIM(RTRIM(Column1)),LTRIM(RTRIM(Column2)),Column3...

Try message handlers to demote these warnings to information..

Ray and Craig ...
Many thanks for your quality posts

have u enable "Add checkpoints so sequence is restartable on failure" option in job properties

If you use Firstname: Lastname then should get the result.
I may be silly but can you check again if you have concatenated last name or not

You can do your if condition in the following way. Do a lookup on the table for USD Currency and then get any one not nullable column (say for eample colA)from the lookup to transformer. If currency is USD then you will find a lookup and ColA will not be nullable. If currency is not USD then you wil...

Hi.

I have observed number of rows per second will be high at the start of the job and later on number of rows per second will be decreasing.
I believe we may not estimate accurately based on number of rows per second on performance statistics.

Hi,

I believe sparse lookup is not a right option for your scenario interms of performance.