SQL Power Software Forum

Hi,

This tool is quite useful. I like the interface.

How does it compare to ERWIN? I like the fact that you can source multiple db's in this tool.

M.

Hi Michael,

For a new user, I believe the Architect is a lot easier to learn than ERwin. For seasoned users of ERwin, obviously there will be a bit of a learning curve while mapping your existing knowledge from ERwin to the Architect.

Beyond that, here are some advantages of the Architect:

The Architect is currently free-to-use for individuals and academic institutions. As of July 7, it will in fact be free for everyone, and better yet.. open source, under a BSD-style license!
Works great on any platform with a Java runtime environment which supports Swing. We actively support and test on the Mac OS X, Windows, and X11 (Linux, *BSD) Swing implementations.

The benefit here is, if you don't use Windows, or even if one person on your team doesn't use Windows, the Architect will be your tool of choice.
Tracks the original source of each column that was originally created by reverse engineering into your working space (the "Play Pen"). Afterward, you can use this information to generate a visual source->target mapping report, or even a data migration job for the open source Kettle ETL tool.
The Architect provides an easy-to-learn and modular Java API for all the operations you can do in the GUI. This means programmers and systems integrators can leverage their knowledge of the Architect by embedding pieces of it (or even the whole thing) into other special-purpose products.
Reverse engineering (a common operation in many data modeling exercises) is an extremely simple drag-and-drop operation in the Architect. In ERwin, it is a cumbersome multi-step process.
Finally, the Architect's "auto layout" feature is ridiculously fun to watch. You have to see it for yourself to know what I mean. Download it now!

Of course, ERwin has a multi-year head start on the Architect in terms of features and maturity. It supports forward engineering to about 10 times more database platforms than Architect does; multiple subject areas; data type domains; separate logical and physical data models; multiple diagram notations, etc.

However, I truly believe the Architect has already made a great start, and it is useful for a growing number of real-world data modeling activities. Try it for yourself and let us know what you think.

-Jonathan