April 21, 2014
Today we will discuss about how Talend – Netezza interactwith each other , along with a simple demonstration that will use the available Netezza components.
you will find all Netezza related components in Palette available.
STEPS : –
1) Installing NZJDBC,jar :- Initially when you drag any of Netezza component from the Palette , and if your library does not contain required .jar to support those components then it will throw an error as shown below.
This means your TOS do not have supported .jar
Immediately a popup will come which will automatically install the required drivers. However if it fails to install the required .jar then you have to manually place that jar file.
(a) Download nzjdbc.jar from the internet.
(b) Copy downloaded .jar file into this location (C:\TOS\TOS_DI-Win32-r101800-V5.3.0\lib\java)
(c) Save your Current Job and Re-Start TOS (Talend Open Studio).
Now you are set to go ,just drag and drop your required components from the palette and connect them as per the business requirement.
This below job will show a simple Talend Netezaa Interaction and will create an excel file from a Netezza Database Table.
A) Drag tNetezzaConnection from the palette and fill all required entries like Host , DB-Name and Password
B) Now to Read data from a table drag tNetezzaInput and specify attributes such as table Name and write your SQL like
(select emp_id , ename from emp limit 100) *It will only fetch 100 rows from the employee table
C) At final to populate the row/data to some output( Excel file ) drop this component to the designer area.
D) Connect All components as shown in figure.
E) Save and Run The Job.
Talend Netezza Interaction Successful …
Check out our other posts on Talend Interview Questions…
Author : – Ankit Kansal & Nayan Naik
June 26, 2013
- shared_conn_demo–>> This job holds our two child jobs (parent,child)
- parent_db_conns–>>The primary job is the one in which connection(shared) is registered for our sub jobs.
- child_job_conn–>>This is the third job which will be using the connection created in parent job.
just fill all the enteries required to create a connection here.
and leave all the field blanks.
2) shared_conn_demo:-Now you just have to connect both the jobs and then run them.
Give the trigger as OnSubjobOk
That’s it now you can use or share your connections through out your all jobs and save connections.
Thank you for reading…
June 22, 2013
Late arriving dimensions issues are commonly encountered in a datawarehousing environment.
The snapshot below shows the overall mapping to resolve the late arrviving mapping
In this case we consider a type1 Insert/Update SCD dimension table and use a reusable sequence to resolve this issue:
Here is the snapshop of the over all mapping:
These are the overall steps followed:
1)We have 2 dimension tables namely the product dimension and the store dimension ,which are used for fact table loading (sales fact table).
2) We simulated a condition where in the late arriving dimension issue arises in the product dimension while loading into the sales fact table.
3)Add the source table as the sales oltp table .
4)Add two look up transformation for the product and the store dimension.
5)We have added a sequencer named product_dimension_seq , this transformation is reusable sequence transformation that i have used while loading into the product dimension table , this helps me to come up with an SKEY(surrogate key) in case of an late arriving dimension.
6)In the expression dimension
As you can observe in the expression port, we have an out_prod_SKEY where in the following condition is defined “IIF(ISNULL(product_skey),product_seq_NEXTVAL,product_skey)“
where in case the SKEY is NULL we use the sequencer’s value to generate an SKEY.
6)Now we have to targets in the flow:
i)We use a filter transformation to find the product_SKEY is null and load it into the dimension table with the value from the sequence generator , since the product dimension is an Insert else Update, whenever the dimension arrives the values will be updated.
ii)Now since we have an SKEY for the missing or late dimension , we now load the data into the sales fact table.
This will solve the late dimension issue . Thanks for reading !!!!!!
In case of any queries please do comment…..
May 9, 2013
All of the dimension tables are SCD-type implemented other than TIME DIMENSION.
April 10, 2013
1)From tOracleInput_3 bring the max surrogate key present in your dimension table using query
“SELECT max(user_profile_sur_key) FROM ANKIT_KANSAL.user_profile”
USER PROFILE IS OUR DIMENSION TABKE
4) tOracleInput4 takes all your data from the source oracle system KEEP ALL THE SOURCE AS A VARCHAR2 FORMAT ONLY.
5)using tMap component calculate your date and also you can find out your GOOD and BAD records depending upon the business requiremetns.
|In the value part perform these operations|
|checking tweet_id is numeric or not|
6) Finally load the data using running the job.
NOW SCD TYPE 2 IMPLEMENTATION
In the above figure
tOracleInput_1 contains the staging data.
tOracleInput_2 contains the data from the dimension table thus lookup from the dimension table must be performed to check weather the record exists or not.
|creating the relationship using equi join|
Thank you for taking interest…
March 28, 2013
Hello reader,today we ll try and see how we can attain SCD-2(Slowly changing dimensions) implementation in informatica.
1.assumed the source and target definitions are defined
2.assumed you have a basic understanding of SCD implementations.
3.possess the basic understanding of adding connections to the components.
4.possess basic understanding of working of all components used in the mapping.
Please have a look at the overall mapping.We will discuss each of them part by part in detail.
Lets explore this in detail:
1)Drag drop the Source onto your mapping.
2)Drag drop all the transformations required as shown in image above.