top button
Flag Notify
    Connect to us
      Facebook Login
      Site Registration Why to Join

Facebook Login
Site Registration

Whats the benifit of creating table definition manually in informatica (Source Analyzer) instead of importing

+2 votes
101 views

For importing source/target tables, we can either go for importing them from DB/Flat Files/XML Files OR creating the table definition in informatica itself. I have couple of questions here -
•Whats the benifit of creating table definition manuallu in informatica over importing?
•How can we connect that created table definition to the corresponding data source which could be a DB/Flat file/XML etc.
•Please give a scenario where we create table definitions in informatica rather than importing.

Appreciate your interest.

posted Mar 26, 2014 by Pooja Bhanout

Share this question
Facebook Share Button Twitter Share Button Google+ Share Button LinkedIn Share Button Multiple Social Share Button

1 Answer

0 votes

1.There are no "benefits" - I guess it's only an option when you've got the definition, but not the sample. E.g. database object have not been created yet, or are not yet accessible, yet you're starting development already.
2.But the only useful scenario I know is editing - it's far quicker to edit source than import the source if you need to change just length or naming of one column.
3.IMPORTANT NOTE: Source definitions are never connected to any single source instance. This is to represent a structure that will be accessed in future without pointing to any specific table, database, or even server.

answer Mar 26, 2014 by Shweta Singh
Similar Questions
+4 votes

For importing source/target tables, we can either go for importing them from DB/Flat Files/XML Files OR creating the table definition in informatica itself. I have couple of questions here -

• Whats the benifit of creating table definition manually in informatica over importing?
• How can we connect that created table definition to the corresponding data source which could be a DB/Flat file/XML etc.
• Please give a scenario where we create table definitions in informatica rather than importing.

+1 vote

In Informatica, When I am trying to import a source definition from db (oracle data source) I get below error

[microsoft][odbc driver manager] the specified dsn contains an architecture mismatch between the driver and application

What I understood after doing some surfing is Informaitca is trying to access

C:\Windows\SysWOW64\odbcad32.exe

and not C:\Windows\system32\odbcad32.exe

When I try adding system/user data source (in C:\Windows\system32\odbcad32.exe), I am not able to see oracle.

Please help to get this issue resolved.

0 votes

I have the following table with the shown data in it:

send_date | household_ID

11-20-2014 | 123
11-20-2014 | 456
11-15-2014 | 789

I need to do 2 things:

1) Calculate the max value for send_date

2) Filter out any rows whose send_date does not match that value

In other words, I want the output to be:

send_date | household_ID

11-20-2014 | 123
11-20-2014 | 456

Row number 3 should be filtered out as its send_date is not the max.

I tried creating an aggregate, grouping by all columns, and creating a new output port called MAX_DATE with an expression of MAX(SEND_DATE), then have a filter transformation with the condition MAX_DATE = SEND_DATE

This lets all rows through, though. What can I do to make this work....

0 votes

Using Informatica designer, is there a way to run a complex SELECT statement as-is against a source database, and workflow it into a target table? For example, SQL Server Integration Services makes it really easy to create source/target connections, paste your source SQL, and map the results to the target table. When the package is run, SQL runs against the source, and results are dumped into the target.

Is something like that available in Informatica?

Contact Us
+91 9880187415
sales@queryhome.net
support@queryhome.net
#280, 3rd floor, 5th Main
6th Sector, HSR Layout
Bangalore-560102
Karnataka INDIA.
QUERY HOME
...