What I like most is how complete the modeling workflow is once you know the tool well. I can start from an existing Oracle schema through reverse engineering, review the generated relational model, organize large diagrams into subviews, validate PK/FK relationships and constraints, and then generate DDL from the same model. That end-to-end flow is very practical because the model becomes both documentation and a working design artifact.

I also value the level of control it gives over physical details such as datatypes, naming, keys, indexes, and relationships. It is especially strong in Oracle environments, where the terminology and generated structures are very consistent with the database. The UI is not the most modern, but for detailed database modeling I prefer the depth and precision it provides over more visually polished tools. Review collected by and hosted on G2.com.

What I dislike most is that the tool can feel heavy and dated when working with large or frequently changing models. Once a relational model grows, diagrams become difficult to navigate and usually need to be split into subviews to remain usable.

The compare/merge and synchronization features are powerful, but they are not always intuitive, so I normally review generated changes carefully before applying them.

Collaboration is another weak point. Version control is possible, but the experience is still much more file-based than in modern cloud modeling tools, and there is no real-time collaborative workflow.

I also find that some repetitive modeling tasks could be automated better. For example, smarter suggestions for relationships, datatype mapping, naming standards, or impact analysis would make the tool much more efficient. Review collected by and hosted on G2.com.