Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: ER/Win vs Designer/2000 - Which is better?

Re: ER/Win vs Designer/2000 - Which is better?

From: Robert Miller <rwmiller_at_gte.net>
Date: 1997/04/07
Message-ID: <33495C83.3FC8@gte.net>#1/1

David Ng wrote:
>
> Nathan Secrist wrote:
> >
> > Database Designers/DBAs:
> >
> > We are in the process of evaluating ER/Win and Designer/2000 for
> > our Case Tool/Data Modeling Tool.
> >
> > We will be using the software for the following tasks:
> >
> > Entity-Relationship Diagrams
> > Logical Modeling
> > Physical Modeling
> > Maintaining a Data Repository
> > Automatically generate Oracle DDL from the Repository
> > Reverse Re-Engineer Oracle Tables back into the repository
> >
> > If anyone can give me some feedback on whether or not you have
> > used 1 or both of these tools.
> >
> > Let me know your experience (good or bad) with each of these tools.
> >
> > If there is other software we should look at please let me know this
> > as well.
> >
> > Thanks in advance!
> >
> >
> > Nathan
> >
> > Nathan G. Secrist
> > Evolving Systems Inc.
> > nsecrist_at_evolving.com
>
> I was a System Architect. Being a database designer, I prefer ER/Win
> a lot for it easy of use and bi-directional synchronization between
> database schema and the repository. On the other hand, I like Desginer
> 2000 for covering the whole cycle of the development, analysis,
> desginer, development etc..
>
> If you are database designer and working on a small project, ER/Win
> should be you choice. If you are project manager or working on a large
> application development, Desginer 2000 should be your choice.
>
> David Ng

From what I've seen of Erwin's Oracle schema generator, I was not impressed. Perhaps it was due to cockpit trouble on the part of the designer. (sorry, modeler...)

Instead of generating declarative referential integrity constraints when foreign keys are specified, the thing create a trigger for every foreign key. This is not desirable in Oracle, and in earlier releases, there was a limit on the number and type of triggers that can be placed on one table. Also, on earlier releases, triggers were run-time interpreted and this would have created unnecessary performance hits. Received on Mon Apr 07 1997 - 00:00:00 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US