Skip to main content

Queries in Informatica

By
Queries in informatica are useful in many ways. We can use it to identify mappings across repository in which a particular table is being used.We can use it to identify invalid objects in repository. We can use it to identify if any changes were made to objects on a given day.We even use them for deployment purpose this has been explained in earlier article. Please find the link below
http://dwbuddy.blogspot.com/2014/01/labelling-and-creating-queries-in.html

Suppose we know only table name and we want to know how it is populated and in which all mappings it is being used across informatica repository. We can achieve this by creating query in following way

In repository manger go to tools there we will be having queries .Click new and give the parameters as mentioned in the screenshot


Upon executing the query i.e. clicking the blue arrow icon all the mappings along with folder name which has table Employee being used will be displayed.

Click save so that query can be used for future purpose

To find the changes made in repository on current day. Create the query in the following way

Upon executing all the objects will be displayed that has been changed in last 1 day we can change the day value upon our requirement.The objects will be displayed along with user name who has changed the objects.
This will be pretty useful if the informatica version is a standard one.

To find any invalid objects in repository



All invalid objects i.e. mappings ,sessions etc will be displayed upon executing the following query

In the above queries you might have noticed that query type as personal/shared. This property is set while saving query under permissions category. If permissions is set to all then it is shared query so every one can use it or else it is personal i.e. only the owner of the query can edit/execute it.

Hope this article helps in understanding informatica queries

Comments

Post a Comment

Popular posts from this blog

Comparing Objects in Informatica

By
We might face a scenario where there may be difference between PRODUCTION v/s SIT version of code or any environment or between different folders in same environment. In here we go for comparison of objects we can compare between mappings,sessions,workflows In Designer it would be present under "Mappings" tab we can find "Compare" option. In workflow manger under "Tasks & Workfows" tab we can find "Compare" option for tasks and workflows comparison respectively. However the easiest and probably the best practice would be by doing using Repository Manager.In Repository Manager under "Edit" tab we can find "Compare" option. The advantage of using Repository manager it compares all the objects at one go i.e. workflow,session and mapping. Hence reducing the effort of individually checking the mapping and session separately. Once we select the folder and corresponding workflow we Can click compare for checking out
11 comments
Read more

Finding Duplicate records and Deleting Duplicate records in TERADATA

By Anonymous
Requirement: Finding duplicates and removing duplicate records by retaining original record in TERADATA Suppose I am working in an office and My boss told me to enter the details of a person who entered in to office. I have below table structure. Create Table DUP_EXAMPLE ( PERSON_NAME VARCHAR2(50), PERSON_AGE INTEGER, ADDRS VARCHAR2(150), PURPOSE VARCHAR2(250), ENTERED_DATE DATE ) If a person enters more than once then I have to insert his details more than once. First time, I inserted below records. INSERT INTO DUP_EXAMPLE VALUES('Krishna reddy','25','BANGALORE','GENERAL',TO_DATE('01-JAN-2014','DD-MON-YYYY')) INSERT INTO DUP_EXAMPLE VALUES('Anirudh Allika','25','HYDERABAD','GENERAL',TO_DATE('01-JAN-2014','DD-MON-YYYY')) INSERT INTO DUP_EXAMPLE VALUES('Ashok Vunnam','25','CHENNAI','INTERVIEW',TO_DATE('01-JAN-2014',
2 comments
Read more

Target Load Type - Normal or Bulk in Session Properties

By
We can see the Target load type ( Normal or Bulk) property in session under Mapping tab and we will go for Bulk to improve the performance of session to load large amount of data. SQL loader utility will be used for Bulk load and it will not create any database logs(redolog and undolog), it directly writes to data file.Transaction can not be rolled back as we don't have database logs.However,Bulk loading is very as compared to Normal loading. In target if you are using Primary Key or Primary Index or any constraints you can't use Bulk mode. We can see this property in the below snap shot.
Post a Comment
Read more