Q:

My client presently uses ETI Extract and custom-built code for many data migration projects but purchased Informatica and is planning to migrate to Informatica. Any pointers on setup issues, setting up various environments (test/stage/prod), handling concurrent projects, how to migrate code from test to production etc.?

A:

Mike Jennings’ Answer: Some items to consider in planning and implementation of your environment are:
  • Decide how repositories and folders are going to be segmented. If the same group of developers is going to be used across projects you may want to consider setting up a repository for each environment (DEV/QA/UAT/PROD) with folder groups for each project plus a folder to share transformation maps and maplets. Project leads can be given administration rights to their respective area.
  • Large migrations can be handled using the repository manager folder copying utility. Smaller migrations can use the XML import/export facility to move individual transformations.
  • Naming standards should be established for transformation objects, maplets, sessions, batches and ports that I used on all projects, which include an abbreviation of the transformation type. This will facilitate sharing of objects across projects.

Register or login for access to this item and much more

All Information Management content is archived after seven days.

Community members receive:
  • All recent and archived articles
  • Conference offers and updates
  • A full menu of enewsletter options
  • Web seminars, white papers, ebooks

Don't have an account? Register for Free Unlimited Access