Skip to main content

Labelling and creating queries in informatica

Informatica components i.e. mappings,session,workflows,transformation are moved from one environment to another environment say from development to SIT can be done in various ways such as
--Export the xml's and again import the xml's in the respective environment
--Drag and Drop objects from one repository to another repository
For the above process to be done you should have required access across environments.

One other way is labelling the components and then creating queries in repository manager. Using these queries components are moved across environment's

We need to go to the repository manager and select the version tab and select label



Then click new label and give a name say "Wf Migration" and click OK. There we  have permissions tab where we can give access to other users to use the same label.

Now we need to select the workflow which needs to be promoted to higher environment.  Right click on workflow and select "view dependencies"





and select all children ,all parents options. Upon which  a window will open with all the components depended on that workflow.

Select all the components and then right click and select  label option and click apply label and select our label "Wf Migration". This is if we want all the components to be migrated, suppose if we made a change only in a particular transformation say in a filter transformation, then select only filter transformation and do the above process.Now labelling is completed.

PS: Note down the count of  no. of components labelled under the label

Queries are used to identify the labelled components we need go tool options in repository manager and then click queries




Give query a name in here we have options under query conditions such as folder name,label,check in time,business name etc. we need to select label option and in there we need to select our label and then save it.

We have execute option i.e.a blue right arrow upon executing the query it will return all the components under the specified label. The count of the no of components under the query result should be equal to label count which we noted down earlier.

These queries are used to migrate the components using migration tools. Each query can have multiple labels.

Hope this article helps you in understanding the labelling & queries concept

Comments

  1. But why do we need it? any specific advantage with lable method?

    ReplyDelete
  2. Great and I have a neat present: Where To Buy Houses That Need Renovation updating exterior of home

    ReplyDelete

Post a Comment

Popular posts from this blog

Comparing Objects in Informatica

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 ...

Target Load Type - Normal or Bulk in Session Properties

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.

SCD Type 2 Implementation in Informatica using dynamic lookup

We have already covered how a dynamic look up works the same can be found out from the following link http://dwbuddy.blogspot.com/2014/06/dynamic-look-up-in-informatica.html  So let's see how we can use it in a regular SCD type 2 mapping. The logic used in SCD type 2 is same as discussed in earlier blog i.e.  http://dwbuddy.blogspot.com/2015/01/scd-type-ii-implementation-in.html . The only difference being here is we have used dynamic look up instead of a static one. We go for dynamic look up when there are duplicate entries for a PK value and only the latest record present in the file should be termed as active. Let us consider the following sample data So  for EMP_ID 101 we have two records in the same day flow so the latest record i.e. with salary as 1500 should be termed as Active record. The mapping will look in the following way So in here we have a dynamic lookup couple of expression transformations,a transaction control transformation which is use...