Best Practices for Organizing Metadata in DataStage
Posted: Mon Sep 20, 2004 10:22 am
Experts,
We are trying to determine the best approach for organizing the metadata within DataStage. Our environment uses Oracle tables, sequential flat files, and hash files. Any table or file can act as a source and/or target. We have several development initiatives that may share a table definition yet target different schemas (i.e., the Product dimension may be in several schemas). This is an interesting challenge because DataStage automatically prepends the schema name to the table name in the metadata definition.
Any help on how to organize the Categories within the metadata and instill a process that maximizes reusability and modularity would be greatly appreciated.
Thanks in advance,
Rick Young
SEI - Atlanta
A Systems Evolution Company
We are trying to determine the best approach for organizing the metadata within DataStage. Our environment uses Oracle tables, sequential flat files, and hash files. Any table or file can act as a source and/or target. We have several development initiatives that may share a table definition yet target different schemas (i.e., the Product dimension may be in several schemas). This is an interesting challenge because DataStage automatically prepends the schema name to the table name in the metadata definition.
Any help on how to organize the Categories within the metadata and instill a process that maximizes reusability and modularity would be greatly appreciated.
Thanks in advance,
Rick Young
SEI - Atlanta
A Systems Evolution Company