Logical to Physical Data Model Transformations

[smither]

We have a fully normalised corporate data model, expressed as a class model in EA. It is the basis for multiple physical models which all need tailoring for their target environment.  For example, we want to maintain scoped denormalised operational models for use in OLTP applications, a normalised model for centralising and unifying the data from disparate legacy systems, and dimensional models for multiple data marts.
I generate a 'table' model using the EA 'DDL Transform' and then use the Code Engineering 'Generate DDL' function to create the DDL for the target DBMS. That all works fine but when I try to generate a second table model by pointing the transformation at a new target package, the transformation engine creates an empty package structure but updates the tables generated from the first transformation.  
How can I generate multiple table models from one logical class model?

[Paolo F Cantoni]

Hi smither,

I tried some transformations early in the piece and I found EA's mechanism to be a mite fragile.

I take it you ARE creating differently named transformations for each distinct transform you are enabling.

AFAIR you should be able to generate multiple targets for the same source element - so long as it has it's own named transform and targets a DIFFERENT element in a different package.

What you need to do is to create copies of the DDL transform and name them for each transform you want.

You can check the database to see the mechanism EA uses (and then shake your head).

HTH,
Paolo

[smither]

Thanks Paolo,
That was the missing piece.  Creating a clone of the transforms works - its just a bit of a pain to keep them all in sync.  

'A mite fragile' is a bit of an understatement .. severely neglected might be more accurate!

Do you know where the 'Generate DDL....' templates are stored and whether they can be modified?  We want to extend some of the generated constructs (e.g. specifying the table Filegroup in SQL Server 2008).