Parameterizing table structures.
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Hi,
I am also having a similar issue.
I tried using the schema file as a parameter for the sequential file stage(which is the source) and it works perfectly.
The problem starts when i try to parameterise the target table, as i dont see any option to use a schema file in any of the DBMS stages.
That means i am able to parameterise the source file name, souce file definition and the target name, but not the target table definition and under these conditions my metadata for the source and target are not matching.
I am also having a similar issue.
I tried using the schema file as a parameter for the sequential file stage(which is the source) and it works perfectly.
The problem starts when i try to parameterise the target table, as i dont see any option to use a schema file in any of the DBMS stages.
That means i am able to parameterise the source file name, souce file definition and the target name, but not the target table definition and under these conditions my metadata for the source and target are not matching.
Ray's preferred approach would also be my preferred approach.
Maintainability is an important factor. Having the metadata for impact analysis and data lineage is extremely important.
It's true that Ab Initio can do this easily with a parameterized graph, but if an Ab Initio developer took the time to make sure that data lineage and impact analysis was not broken... Instead they generally don't take care of the metadata, which is one reason (in my opinion) that Ab Initio's metadata solution is so weak.
Mike
Maintainability is an important factor. Having the metadata for impact analysis and data lineage is extremely important.
It's true that Ab Initio can do this easily with a parameterized graph, but if an Ab Initio developer took the time to make sure that data lineage and impact analysis was not broken... Instead they generally don't take care of the metadata, which is one reason (in my opinion) that Ab Initio's metadata solution is so weak.
Mike
Does anyone know what MDB's suggestion does to impact analysis and data lineage? Is it broken? Can it be easily fixed? If it is broken and takes anything more than trivial developer effort to fix, then I personally will avoid this technique. I place much greater value on metadata and maintainability than I do on a minor productivity gain.
Mike
Mike
Mike..
With all regards, i totally accord with the fact of making 10 Different jobs for "impact analysis and data lineage".
But my post was mistaken by you perhaps. It was just to let "Karthi" know, who was trying to acheive re-usability(in a single job), how to do that irrespective of the Maintenance factor.
& Karthi, i trust you must have got what you need to do :D
With all regards, i totally accord with the fact of making 10 Different jobs for "impact analysis and data lineage".
But my post was mistaken by you perhaps. It was just to let "Karthi" know, who was trying to acheive re-usability(in a single job), how to do that irrespective of the Maintenance factor.
& Karthi, i trust you must have got what you need to do :D
Rgds,
MB
MB
MDB,
To the contrary, I really appreciate the suggestion that you offered. For my own education, I just want to understand the pros and cons of different design alternatives. I don't have a good feel for the current metadata capabilities in Information Server and haven't done anything with metadata since my return to the DataStage world. I suspect the "utility" approach would break data lineage and impact analysis in IIS as well... just want to confirm that suspicion and see if it is "repairable".
Mike
To the contrary, I really appreciate the suggestion that you offered. For my own education, I just want to understand the pros and cons of different design alternatives. I don't have a good feel for the current metadata capabilities in Information Server and haven't done anything with metadata since my return to the DataStage world. I suspect the "utility" approach would break data lineage and impact analysis in IIS as well... just want to confirm that suspicion and see if it is "repairable".
Mike