what is the difference between repository & Intergration service
what is the difference between repository & Integration service?
Repository: consist of original data base tables which are also called as system tables and metadata objects.
Ex:Actual source data (customers data,employee data,sales data)
Repository service: Repository service is responsible for inserts,updates,deletes and retrieve metadata from Repository. so it will work like mediator between the Repository and Integration Service(client components).
Ex: if you want to extract the data from Repository(actual data) at run time through Integration service you'll get an error because IS doesn't understand the System tables directly so you will need Repository service to handle inserts,updates,deletes and retrieve the data from Repository.
Integration Service: IS is responsible for executing the ETL Objects and performs Extraction,Transformation and Loading at Run time(while executing the session).IS needs Original database objects using objects we can move the data from source to target as per the requirements.
Ex: if you have a business requirements like calculations and conversions all these done by the IS.
| Is This Answer Correct ? | 1 Yes | 0 No |
I am getting five sources in a day and i donot know when i get them. i need to load data into the target and run the session. but here i can't keep the session in running or can't stop the session. plz help me
Give one example for each of conditional aggregation, non-aggregate expression, and nested aggregation?
Can we write to_date(three arguments) ? Will it work ? Advance thanks
performance wise which one is better in joiner and lookup transformation?why?explain clearly?
How to update source definition?
what is polling?
when load type is selected as bulk or normal in session level ?let me know the internal process and give me an example?
If in a workflow i have n number of sessions and each session is configured with different different stop on errors (say 5,8,10 etc respectively).How can make all this same for all the sessions with out actualy touching each and evry session ?
My Source qualifier has empno, sal. Now my mapping is like SQ(EMPNO)->AGGR->EXP->TARGET SAL ------------>TARGET ? means only one source qualifier has 2 columns like empno, sal. connected to same target as shown in above mapping.Is this mapping valid or any issues are there if we design like this?
How many dimensions are there in informatica?
Where are the source flat files kept before running the session?
Quickly characterize reusable change?