Skip to main content

Joiner Transformation Interview Question ( Part - 1)

By

What is a Joiner Transformation and why it is an Active one?
 
Answer:


A Joiner is an Active and Connected transformation used to join two source data streams coming from same or heterogeneous databases or files.

The Joiner transformation joins sources with at least one matching column. The Joiner transformation uses a condition that matches one or more pairs of columns between the two sources.

In the Joiner transformation, we must configure the transformation properties namely Join Condition, Join Type and optionally Sorted Input option to improve Integration Service performance.

The join condition contains ports from both input sources that must match for the Integration Service to join two rows. Depending on the join condition and the type of join selected, the Integration Service either adds the row to the result set or discards the row. Because of this reason, the number of rows in Joiner output may not be equal to the number of rows in Joiner Input. This is why Joiner is considered an Active transformation.

State the limitations where we cannot use Joiner in the mapping pipeline.

Answer:


The Joiner transformation accepts input from most transformations. However, following are the limitations:

Joiner transformation cannot be used when either of the input pipelines contains an Update Strategy transformation.

Joiner transformation cannot be used if we connect a Sequence Generator transformation directly before the Joiner transformation.




Out of the two input pipelines of a joiner, which one will we set as the master pipeline?

Answer:
 
During a session run, the Integration Service compares each row of the master source against the detail source. The master and detail sources need to be configured for optimal performance.

When the Integration Service processes an unsorted Joiner transformation, it blocks the detail source while it caches rows from the master source. Once the Integration Service finishes reading and caching all master rows, it unblocks the detail source and reads the detail rows. This is why if we have the source containing fewer input rows in master, the cache size will be smaller, thereby improving the performance.
 
For a Sorted Joiner transformation, use the source with fewer duplicate key values as the master source for optimal performance and disk storage. When the Integration Service processes a sorted Joiner transformation, it caches rows for one hundred keys at a time. If the master source contains many rows with the same key value, the Integration Service must cache more rows, and performance can be slowed.



What are the different types of Joins available in Joiner Transformation?


Answer:

In SQL, a join is a relational operator that combines data from multiple tables into a single result set. The Joiner transformation is similar to an SQL join except that data can originate from different types of sources.

The Joiner transformation supports the following types of joins:

Normal

Master Outer

Detail Outer

Full Outer

Joiner Transformation Interview Question ( Part - 1)
Joiner Transformation Interview Question ( Part - 1)


A normal or master outer join performs faster than a full outer or detail outer join.
Labels:

Comments

  1. Unknown1 September 2016 at 04:57

    Awesome blog very well defined stuff thanks for sharing.

    ReplyDelete
  2. Anonymous3 April 2018 at 03:28

    For maximum depth, use reduced frequencies.

    ReplyDelete

Post a Comment

Popular posts from this blog

Contact Me

By
Do You have any queries ?                   If you are having any query or wishing to get any type of help related Datawarehouse, OBIEE, OBIA, OAC then please e-email on below. I will reply to your email within 24 hrs. If I didn’t reply to you within 24 Hrs., Please be patience, I must be busy in some work. kashif7222@gmail.com
3 comments
Read more

Top 130 SQL Interview Questions And Answers

By
1. Display the dept information from department table.   Select   *   from   dept; 2. Display the details of all employees   Select * from emp; 3. Display the name and job for all employees    Select ename ,job from emp; 4. Display name and salary for all employees.   Select ename   , sal   from emp;   5. Display employee number and total salary   for each employee. Select empno, sal+comm from emp; 6. Display employee name and annual salary for all employees.   Select empno,empname,12*sal+nvl(comm,0) annualsal from emp; 7. Display the names of all employees who are working in department number 10   Select ename from emp where deptno=10; 8. Display the names of all employees working as   clerks and drawing a salary more than 3000   Select ename from emp where job=’clerk’and sal>3000; 9. Display employee number and names for employees who earn commissi...
32 comments
Read more

Informatica sample project

By
Informatica sample project - 1 CareFirst – Blue Cross Blue Shield, Maryland (April 2009 – Current) Senior ETL Developer/Lead Model Office DWH Implementation (April 2009 – Current) CareFirst Blue Cross Blue Shield is one of the leading health care insurance provided in Atlantic region of United States covering Maryland, Delaware and Washington DC. Model Office project was built to create data warehouse for multiple subject areas including Members, Claims, and Revenue etc. The project was to provide data into EDM and to third party vendor (Verisk) to develop cubes based on data provided into EDM. I was responsible for analyzing source systems data, designing and developing ETL mappings. I was also responsible for coordinating testing with analysts and users. Responsibilities: ·          Interacted with Data Modelers and Business Analysts to understand the requirements and the impact of the ETL on the business. ·  ...
Post a Comment
Read more