- Logically create the folders / subfolders on the file server so that the files can be placed and accessed from the relevant folders/subfolders.
- Group the Jobs logically into various categories / Subcategories.
- Comment the Jobs by using Annotation stage which tells the users, the functionality implemented in the job.
- Give descriptions in the properties of the stages used so that others can identify the functionality implemented in it.
- Name passive stages with the Table/File Names they access in it. 6. Name active stages to match their function.
- Name links to express the direction and type of data flowing through them.
- Use job parameters where ever it is required. This makes the process easy while moving into production.
- While using ODBC stages remember to remove the derivations in the columns.
- Use ODBC stage to access relational tables.
- Move constraints from Transform stages to input stage WHERE clauses, to reduce the number of rows the job has to process.
- Use the in-built functions present in Data Stage rather than creating a new routine for implementing the same logic as of in-built function.
- Open the transformer stage
- Copy the columns from source(ODBC ) to target(Sequential File)
- Delete the columns from source(ODBC)
- Copy all the columns from target to the source.
- Close the transformer.
- Now we find that all the derivations are cleared from ODBC stage.
While using Reference Lookups
- Compare the number of input rows with the number of rows in the reference table. If the reference table is smaller than the number of input rows, pre-load the reference table into a hash file and then reference the hash file.
- Consider moving reference lookups to a join within the input stage. All columns used to join the tables should be indexed to maximize performance.
- If the number of rows in a hashed file is small, consider Pre-loading the file into memory by checking the Pre-load file to memory checkbox in the Hash File stage.
- Remove unused columns from transforms. This does not apply to columns in sequential files or output to hash files.
- While mapping the input records with the Hash Look ups, remember that the fields getting mapped should be of same data type and of same length.
- While loading the hash files, trim the data.