For handling the NULL value in columns we can use modify functions in DataStage instead of Transformer. Rather, I'll always prefer a transformer to avoid unnecessary effort which we put to setting up modify stage. But sometime to tune the job over performance we have to do that ;-)
The below Function Specification we have to use to Handle NULL --
Something about DataStage, DataStage Administration, Job Designing,Developing, DataStage troubleshooting, DataStage Installation & Configuration, ETL, DataWareHousing, DB2, Teradata, Oracle and Scripting.
Showing posts with label handling. Show all posts
Showing posts with label handling. Show all posts
Tuesday, February 03, 2015
Monday, February 17, 2014
Datastage Coding Checklist
- Ensure that the null handling properties are taken care for all the nullable fields. Do not set the null field value to some value which may be present in the source.
- Ensure that all the character fields are trimmed before any processing. Normally extra spaces in the data may lead to some errors like lookup mismatch which are hard to detect.
- Always save the metadata (for source, target or lookup definitions) in the repository to ensure re usability and consistency.
Friday, November 22, 2013
ETL Job Design Standards - 2
This section defines standards to manage job parameters
across environments. Jobs should use parameters liberally to avoid hard coding
as much as possible. Some categories of parameters include:
- Environmental parameters, such as directory names, file names, etc.
- Database connection parameters
- Notification email addresses
- Processing options, such as degree of parallelism
Labels:
Administration
,
Data
,
DataStage
,
design
,
ETL
,
exception
,
handling
,
Job
,
load
,
notification
,
Optimizing
,
parameter
,
performance
,
report
,
source
,
Standards
,
statistics
,
tips
Tuesday, November 12, 2013
ETL Job Design Standards - 1
When using an off-the-shelf ETL tool, principles for
software development do not change: we want our code to be reusable, robust,
flexible, and manageable. To assist in the development, a set of best practices
should be created for the implementation to follow. Failure to implement these
practices usually result in problems further down the track, such as a higher
cost of future development, increased time spent on administration tasks, and
problems with reliability.
Although these standards are listed as taking place in ETL
Physical Design, it is ideal that they be done before the prototype if
possible. Once they are established once, they should be able to be re-used for
future increments and only need to be reviewed.
Listed below are some standard best practice categories that
should be identified on a typical project.
Labels:
database
,
DataStage
,
design
,
environment
,
Errors
,
ETL
,
handling
,
Job
,
Link
,
managers
,
Metadata
,
names
,
notification
,
Optimizing
,
parameter
,
process
,
reusability
,
stages
Subscribe to:
Posts
(
Atom
)