Informatica Standards: Difference between revisions
Jump to navigation
Jump to search
| Line 6: | Line 6: | ||
<LI>Always check "Run if previous completed" on command tasks</LI> | <LI>Always check "Run if previous completed" on command tasks</LI> | ||
<LI>Try to avoid overriding reuseable Tasks and Sessions... if you get a "Revert" button while making a change, make sure the change should only apply to THIS instance, rather than every instance, and consider making the change in another place.</LI> | <LI>Try to avoid overriding reuseable Tasks and Sessions... if you get a "Revert" button while making a change, make sure the change should only apply to THIS instance, rather than every instance, and consider making the change in another place.</LI> | ||
<LI>Scripts should always write to <stdout>; only the highest level call should redirect to a log file with "> <log> 2>&1" style</LI> | |||
</UL> | </UL> | ||
Revision as of 20:18, 22 August 2007
Informatica Standards and Thoughts
Good Standards
- Always set the error threshold to 1
- Always check "fail parent if this task fails"
- Always check "Run if previous completed" on command tasks
- Try to avoid overriding reuseable Tasks and Sessions... if you get a "Revert" button while making a change, make sure the change should only apply to THIS instance, rather than every instance, and consider making the change in another place.
- Scripts should always write to <stdout>; only the highest level call should redirect to a log file with "> <log> 2>&1" style
Discussion Items
- Where should shell script redirects to log files be? In the Informatica command task that calls them? Should the script handle its own log file? If a BTEQ script is called from a shell script, should the shell script handle the BTEQ log but something else handle the shell script log? Or should the BTEQ just pass through stdout and stderr to the script, which is then redirected by Informatica?