Most case tools can be used for logical and physical modelling. In
PowerDesigner you have two completely separated models for this. It is
possible to transfer your model from the logical to the physical model
(and vice versa). You can generate your database code for different
database systems. It is also possible to import existing database
structures to the physical model. This gives you a good starting point
for documentation and reengineering purposes. In addition, it is
possible to built up code generators from the scratch or to customize
them to your special needs.
I use PowerDesigner not only for logical database modelling but also for
physical modelling and as the only instance to manage all database code
including tablespaces, users, tables, keys indexes, triggers, stored
procedures, sequences, roles, grants etc. in one place. So it is easy
for me to keep the overview and to document my systems.
But be aware, it is one of the most expesive systems on the market.
--
All emails sent to this address are never read and never will be
answered. Sorry, but until someone cleans up the spam mess, that's the
way it has to be.
E-Mails, die direkt an diese Adresse geschickt werden, lese und
beantworte ich nicht. Ich bedauere diesen Umstand sehr, kenne derzeit
aber keine bessere Möglichkeit, um die Spam-Flut abzustellen.
Mit freundlichen Grüßen / Best Regards
Michael Gast
SEPP MED GmbH
Received on Fri Nov 15 2002 - 09:16:30 CET
