Archives of the TeradataForum

Message Posted: Wed, 30 Nov 2005 @ 20:49:03 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

<-- Anonymously Posted: Wednesday, November 30, 2005 15:09 -->

I am not sure why you would like to do it that way but that's a preference for an individual to make in how they use a CASE tool. I don't believe the intent of a postscript is to issue DDL to add columns.

I use the FORWARD ENGINEERING facility of the tool to generate 100% of our DW database schema and do not get the problems you encounter and use postscripts for PPIs. I even made quick test like yours to proof it and it works fine too.

The primary purpose of ERwin is to model the business and capture metadata. The fact that ERwin generates the DDL is a nice side-effect of the tool. Moreover, I think it would be confusing to have a model in front of me that does not match the database schema (something I have been correcting for the past year after the vendor's modeler left the job site).

If it were me, I would include the attributes in my model via two possible ways:

1. Add the attributes to the Logical and Physical model

2. Add the attributes to the Physical model only

With option 1, the quick way is to COPY and PAST a dummy ENTITY with the two attributes "N" times, where N is the number of entities that will receive the values. Then it's a matter of drag and drop from a copied dummy ENTITY to the target ENTITY, followed by a delete of all the DUMMY entities.

With option 2, you can use the quick way via COPY and PASTE (table in this instance) or you choose to DENORMALIZE from a dummy TABLE the two columns into each target TABLE. More time consuming and not really the intent of denormalization, but it could work.

Regardless, if you choose to make your model more explicit by including the attributes, make sure to use DOMAINS to facilitate data type changes on the fly.

If you still want to use postscript to generate alter statements to add tables you may wish to generate using the Forward Engineering facility or use a BTEQ to run the script.

Anonym

	<Prev	Next>		<<First	<Prev	Next>	Last>>