· We cannot use SQL override while using flat files as source.
· We need to specify correct path in the session and have to mention the file is ‘direct’ or ‘indirect’.
· And keep the file in exact path as mentioned in the session.
· Have to convert the date field to date data type since it reads as string.
Hi Kashif,
ReplyDeleteThanks for your blog. This question is quite interesting. I believe if you frame this question as (suggestion) "Points to be considered while working with flat files" . Since if we always points the issue around some thing then it would give a fear for new bees. Additional point you can consider as
1) File name that comes with date and that date should be extracted then use indirect method and take the last string rather than counting from the beginning since in different env, string length is different.
Please keep writing blogs.
You can contact me at tele.sarkar@gmail.com
Thanks for your extra time for the blog
Thanks for your valuable comment
Delete> If the flat file is in UNIX system, then you need to manage the dos to unix conversion.
ReplyDelete> Handling the null characters
> Special characters
Yes, you are correct.
Deletewhen we use 'output field names' the first field name always start with #
ReplyDeleteMS office might get error in opening Flat file targets generated by informatica with .xls or .xlsx extension.
Need to give 'number of initial rows to skip ' in case of flat file sources/lookups
when we give source file directory does the service search for the file in theat directory only or if it does not find it in that directory, it will search in the sub directories too.
ReplyDeleteIt will search in sub directory too.
Delete