Display optimized sql is not pushdown when we use multiple alias.

[#1]

Hi ,

I have source table with owner owner1. source and target table with owner2. target table.

Both are from same database ( SAP IQ). I need to use data store configurations as I need to connect multiple systems.

I have created two aliases one for source tables and another one for target tables.

I created simple data flow with one one mapping and target table without bulk load options.

If I see the display optimized sql it is showing sql statement instead of insert into statement. If I don't use aliases and import original owner it is showing the insert into statement?

Is any impact of multiple aliases in the data store for puhsdown?

If I am using the multiple aliases, how can I achieve the puhdown?

Thanks & Regards,

Venkata Ramana Paidi.

[Former Member]

Hello Venkata,

I have a datastore which have aliases created for Target and Source. i just created a test job with source ---->Query-----> Target and enabled Bulk loading in the target table and when i see the display optimized sql it starts with SELECT. I then disabled Bulk loading option in the target table and now the display optimized SQL starts with INSERT INTO.

[venkataramana_paidi]

Hi Ravi Kiran,

Thanks for your response.

I thought alias was causing the issue for pushdown. I have found the issue. If we have datatime in the source and date data type in the target, implicit conversion avoid the pushdown. So we need to convert to datetime to date.

Here very strange thing is we should not use to_date(to_char(field1,'yyyy.mm.dd'),'yyyy.mm.dd'). This is also not puhdown. We have to use only to_char(field1,'yyyy.mm.dd')

Thanks & Regards,

Ramana.