Archives of the TeradataForum
Message Posted: Tue, 28 Feb 2006 @ 09:33:05 GMT
<-- Anonymously Posted: Tuesday, February 28, 2006 04:34 -->
Are there any methodologies, self made solutions or any other ways to solve a problem of describing ETL transformations?
Documents I have to use at the moment consisits of following information:
a) input table name (with prefix for db name)
b) input field name (type, length tec.)
c) as above for output
d) transformations, which are described in comments, but what is worse in "free form" way, which means that output of transform depends on how it will be understood by ETL developer!!!
We don't use any quasi-SQL notation or any other formal notations to decribe transforms.
Do you use any?
Would you share it with me or just share the idea?
Thanks in advance
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|