why we use stored procedure transformation?
Answers were Sorted based on User's Feedback
The Stored Procedure Transformation is used to call the
stored procedure.
First, we have to create a Stored procedure in Oracle or SQL
Server.It have 2 types.
one is Connected Stored Procedure and another one is
Unconnected Stored Procedure.
| Is This Answer Correct ? | 5 Yes | 0 No |
Answer / vas.chiky
for complex results, which we cannot obtain in SQL or from
informatica transformation, we go for procedures.
Also doing the calculation in database level doesnt makes
work load high for our informatica server.
process will be given to database.
| Is This Answer Correct ? | 3 Yes | 0 No |
Answer / abhinaw prakash
Valid Stored Procedure Use cases
Complex Calculations
If we have a complex calculation that needs to be done for
each record repeatedly we may use stored procedure
transformation. Complex statistical calculations where a
certain measure is being calculated for each of the record
is a good example where one may want to use this.
Performance
There are cases where you may want to use this to improve
your performance. Let’s say one calculation requires
accessing or looking up multiple records or values from
several different tables. If you were to perform this
calculation in Informatica, you will have to perform
multiple lookup operations in many tables. Depending upon
the types of your lookup, this may involve caching the
entire data or at least making multiple network level calls
to transport these data over the network layer. Instead, if
we use a stored procedure transformation, we can perform the
entire calculation within the database, thereby, eliminating
any need to transport data over the network.
Security
Although rare but sometimes client may have a proprietary
algorithm implemented in database. Client does not want to
let others know about the actual algorithm in use, however,
wishes that we take advantage of this algorithm. If the
algorithm is implemented in database stored procedure and
proper access restrictions are placed, then we will not be
able to read the SP to see the algorithm, but still can call
this from Informatica to take the advantage of the
algorithm. Example, proprietary trading algorithms in banks
and brokerage farms.
Reusability
Reusability is a reason why you may want to use a stored
procedure transformation. Suppose you have already written a
complex code in database programming language, tested the
code exhaustively and you are pleased with the performance
of this piece of code. Now that your Organization is
implementing Informatica, you may not wish to rewrite this
entire piece of code in Informatica again. You can reuse
your existing code through stored procedure transformation.
| Is This Answer Correct ? | 3 Yes | 0 No |
Can you access a repository created in previous version of Informatica?
suppose we have 1 to 10 records.In router transformation we had given two condition A>= 5 A<=5 then what will be the output?
Is there any target staging area in informatica not staging area
There are 4 flat files with number of records as indicated below. Which files should be picked first for joining using joiners so as to get best performance. File A - 1000 records File B - 100 records File c - 10000 records File D - 10 records Please explain. Thanks and Regards,
What if the source is a flat-file?
Can we make worklet inside worklet?
what is constraint based loading
following source name gender ramya female ram male deesha female david male kumar male i want the target male female ram ramya david deesha kumar any body give solution above question?
What is parallel processing in informatica?
how lookup transformation is made active in new versions... When to use connected and when to use unconnected lookup and why? which is good for session performance. How to make lookup persistent and how to remove stale data from that lookup. how commit works - when we stop or abort data. Explain in both cases. What is factless fact table and have you ever used it in real time scenarios.
Why we select the table which has minimum number of records as Master table in joiner?
Explain joiner transformation in informatica