Hi Markus,
I'm not sure whether this offers you any help in your current situation but here is what I do:
1. I never ever update the orm source module by changing the logical db diagram. I always change the conceptual schema and then drop off the logical schema
2. I always create many small aspect specific orm source diagrams and then create a database model diagram and add the source diagrams as existing orm source models to the project, then I build the project therefore mapping from the conceptual schema to the logical schema.
Once in a while, while just playing with the logical schema, it will prompt me to reverse update the source models from the change that I intend to abandon and I will "NEVER" update the source model from the logical since it will make it practically impossible to re-use the same source model in a different project because stuff seems to bleed back that shouldn't.
Wolfgang
From: Markus S. Gallagher [mailto:markus@...]
Sent: Wednesday, June 23, 2004 10:32 AM
To: jcm@yahoogroups.com
Subject: [JCM] Visio Enterprise Architect performance problems with Large Model
tables. VEA requires 3-4 hours to update the source model after I
modifying the Logical Diagram. Is there anything I can do to break my
model into smaller junks and still have relationships across all of the
individual models? Have other people experienced similar type of
performance issues?
Any help is much appreciated - Thanks,
Markus S. Gallagher.
~~~~~~ Sponsor's Message ~~~~~~~~~~~~~~~~~~~~~
Would you like to learn more about Object-Role Modeling (ORM)?
Then check out InConcept's ORM Seminars!
These seminars will focus on the use of Object-Role Modeling to correctly model your business data requirements. Each day also contains "hands on" labs where students practice the technique while ORM-certified instructors give one-on-one assistance.
Custom on-site courses are also available.
For more information, please see http://www.inconcept.com/training/ormseminar.html or e-mail training@....