Re: ER/Win vs Designer/2000 - Which is better?
Posted in 1997
Topics: Performance & Tuning, Triggers, Constraints & Referential Integrity
ERWin's trigger generation is an option that can be suppressed. It is a great strength of the product. We use ERWin extensively. It does a very good job of reverse-engineering our schemas, then forward-engineering our changes. One limitation is the inability to deal with stored Packages, but even though we make extensive use of Packages to encapsulate data, that has not been a significant problem. +----------------------------------------------------- | Dan Townsend, Supervising Database Architect | EBMUD Enterprise Object Designer | mailto:townsend@ebmud.com +----------------------------------------------------- Robert Miller wrote: > 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.