Informaticans

All about Informatica

Informatica Best Practices -1

2.2. Database
2.2.1. Balance between Informatica and the power of SQL and the database. Try to utilize the DBMS for what it was built for, reading/writing/sorting/grouping/filtering data en-masse. Use Informatica for the more outside joins, data integration, multiple source feeds, etc.
2.2.2. Create all the look-ups in the same database. Do not create synonyms, views and tables in other databases.
2.2.3. Write the dynamic SQL commands for executing DDL functions, which would perform activities like Truncate, Create/Drop Indexes etc.
2.2.4. Localize all target tables on to the SAME instance of Oracle (same SID), or same instance of Sybase. Minimize use of synonyms (remote database links) for anything (including: lookups, stored procedures, target tables, sources, functions, privileges, etc.) Utilizing remote links will most certainly slow things down. For Sybase users, remote mounting of databases can definitely be a hindrance to performance.
2.2.5. Create the indexes and constraints only on the Target database
2.2.6. Drop all the indexes before the load is started and re-create the indexes once the load is done for better performance.

Informatica and Database checkpoints:

2.1. Balance between Informatica and the power of SQL and the database. Try to utilize the DBMS for what it was built for, reading/writing/sorting/grouping/filtering data en-masse. Use Informatica for the more outside joins, data integration, multiple source feeds, etc.

2.2. Create all the look-ups in the same database. Do not create synonyms, views and tables in other databases.

2.3. Write the dynamic SQL commands for executing DDL functions, which would perform activities like Truncate, Create/Drop Indexes etc.

2.4. Localize all target tables on to the SAME instance of Oracle (same SID), or same instance of Sybase. Minimize use of synonyms (remote database links) for anything (including: lookups, stored procedures, target tables, sources, functions, privileges, etc.) Utilizing remote links will most certainly slow things down. For Sybase users, remote mounting of databases can definitely be a hindrance to performance.

2.5. Create the indexes and constraints only on the Target database

2.6. Drop all the indexes before the load is started and re-create the indexes once the load is done for better performance.

Comments (0)

  • No comments yet.