New Features of Informatica-9

1. Informatica 9 supports data integration for the cloud as well as on premise. You can integrate the data in cloud applications, as well as run Informatica 9 on cloud infrastructure. 2. Informatica analyst is a new tool available in Informatica 9. 3. There is architectural difference in Informatica 9 compared to previous version. 4. Browser based tool for business analyst is a new feature. 5. Data steward is a new feature. 6. Allows unified administration with a new admin console that enables you to manage power centre and power exchange from the same console. 7. Powerful new capabilities for data quality. 8. Single admin console for data quality, power centre, power exchange and data services. 9. In Informatica 9, Informatica data quality (IDQ) has been further integrated with the Informatica Platform and performance, manageability and reusability have all been significantly enhanced. 10. The mappings rules are shared between the browser based tool for analysts and the eclipse based development leveraging unified metadata underneath. 11. The data services capabilities in Informatica 9 , both over sql and web services ,can be used for real time dash boarding. 12. Informatica data quality provides world wide address validation support with integrated geocoding. 13. The ability to define rules and view and run profiles is available in both the Informatica developer (Thick client) and Informatica analyst (browser based tool-Thin client).these tools sit on a unified metadata infrastructure. Both tools incorporate security features like authentication and authorization ensuring.. 14. The developer tool is now eclipse based and supports both data integration and data quality for enhanced productivity. It provides browser based tool for analysts to support the types of tasks they engage in, such as profiling data, specifying and validating rules & monitoring data quality. 15. There will a velocity methodology. Soon its going to introduce on I9. 16. Informatica has the capability to pull data from IMS, DB2 on series and series and from other several other legacy systems (Mainframe) environment like VSAM, Datacom, and IDMS etc. 17. There are separate tools available for different roles. The Mapping architect for Vision tool is designed for architects and developers to create templates for common data integration patterns saving developers tremendous amount of time. 18. Informatica 9 does not include ESB infrastructure.

19. Informatica supports open interfaces such as web services and can integrate with other tools that support these as well including BPM tool. 20. Informatica 9 complements existing BI architectures by providing immediate access to data through data virtualization, which can supplement the data in existing data warehouse and operational data store. 21. Informatica 9 supports profiling of Mainframe data. Leveraging the Informatica platforms connectivity to Mainframe sources. 22. Informatica 9 will continue support feature of running the same workflow simultaneously. 23. Eclipse based environment is build for developers. 24. Browser based tool is a fully functional interface for business analysts. 25. Dashboards are designed for business executives. 26. There are 3 interfaces through which these capabilities can be accessed. Analyst tool is a browsed tool for analyst and stewards. Developers can use the eclipse based developer tool. Line of business managers can view data quality scorecards

1 Laxmi July 14, 2011 at 4:58 am Hi Murali, Thanks for your posting.I have a small doubt,can we use SQL t/r instead of update strategy t/r in scds.when I was interviewd by a person he was asking me the question like Without using update strategy t/r how can u perform updations & insertions in scd2? Please explain me all possible ways to do this scenario 2 Murali July 14, 2011 at 7:09 pm Hi Laxmi, If you want to perform an insert and update by using SQL transformation definitely we should use the SP, cursors etc..which SQL transformation wont support.The alternative what i can suggest you is you can use router and put two grouos for insert and update then use the two target update/ insert overides. And dont forget to select the appropriate properties(insert/Update) at the session level. 3 Srinivasulu July 20, 2011 at 11:56 am we can use the SQl transformation , but while inserting the records , it will take time to loadi it.

4 Laxmi July 21, 2011 at 5:21 am Thank you Murali.. 5 Laxmi July 21, 2011 at 8:54 am Hi Murali, Can u please explain me in which case we choose update as update,insert else update and delete options..Please explain me with scenario..What happens if i put both update strategy t/r in mapping & enable the above chk boxes in session level?how internally it will work? What is the difference b/n truncate and delete here? if i select both truncate target table and delete options in session with bulk load how it will work? 6 Murali July 23, 2011 at 3:19 am Hi Laxmi, When you configure a session for a respective mapping, you can instruct the informatica Integration Service to either treat all rows in the same way (example, treat all rows as inserts), or use instructions defined into the session mapping to flag rows for different database operations. In PowerCenter, you set the update strategy at two different levels: 1) In the mapping 2) At the session level In the mapping: Within a mapping, you use the Update Strategy trasformation to flag rows for insert, delete, update, or reject. At session level we have the options as metioned below.. Insert > Flags as the rows inserts to the target. Update as update> Flags all the rows as update to the target irrespective of the condition you specified in the update strategy transformation. Update as Insert > Treats updates as inserts. Update else insert > checks for the row in the target and inserts if there is no row exists. If exits it update the particular row in the target. In informatica the mapping level settings will be overriden by session level properties.If you define the same or different properties in the mapping as well as at the session level. The integration service will consider the session level properties we define.

7 tushaR July 25, 2011 at 2:51 pm Hi Murali, I have one quetion reg. SQL transformation.. We are having 20-25 select queries that are fetching records from different table(& some inputs from SQ & EXP) & inserting into ONE target table. I am using SQL tranformation that no. of times for every select query & then inserting the data at target table.. Please can you advice any alternative way to avoid repeataition of SQL tranformation use in mapping. Thanks a lot.