Author Topic: Hard work with DDL diagrams  (Read 2809 times)

Miroslav Fris

  • EA Novice
  • *
  • Posts: 18
  • Karma: +0/-0
  • That's me!
    • View Profile
Hard work with DDL diagrams
« on: February 12, 2003, 02:28:29 am »
Hi,

I'd like just to share my experience.

I imported database tables - about 40 into one diagram. I spent some time to arrange it to be viewable.
The other day one of the table was renamed in the database. I synchronized it with the current model and - there was a new table and an old table as well. After deleting the old one and repeating sync the new/renamed table was without it's associations, so i had to provide them manually - this is not the way I want to sync DDL model, is it?
But the WORST thing. All my arrangment was lost after the sync. Tables and connectors were in one big mess crossing each other.

So table documentation in EA doesn't seem to be good way to manage datamodels - primarily created in database.

I am just windering ybout your experience ....

Mirek

CJ

  • EA User
  • **
  • Posts: 288
  • Karma: +0/-0
    • View Profile
Re: Hard work with DDL diagrams
« Reply #1 on: February 12, 2003, 06:39:34 am »
G'day Mirek,

Although reverse engineering and DDL generation work very well, from my experience I've found synchronization not good at all.

For arranging your model, I'd recommend not trying to arrange the model in the package where you've "imported" the data model.  I've found it much better to create other package(s) and diagram(s), and drag tables from the original package (the one you imported into) to the other diagram(s).  It's a great way to show groups of tables and relationships in different contexts.

My two cents...
« Last Edit: February 12, 2003, 06:40:37 am by jasonv »
Cheers and best regards.

Miroslav Fris

  • EA Novice
  • *
  • Posts: 18
  • Karma: +0/-0
  • That's me!
    • View Profile
Re: Hard work with DDL diagrams
« Reply #2 on: February 16, 2003, 11:52:35 pm »
Thanks for this tip, it sounds very reasonbale. Anyway, printing diagram directly from MS SQL Enterprise manager seems to be faster in some cases.
I'd appreciate the connectors in EA to be smarter - automatically avoid crossing classes for example...