We performed a comparison between erwin Data Modeler by Quest and Sparx Systems Enterprise Architect based on real PeerSpot user reviews.
Find out in this report how the two Enterprise Architecture Management solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI.
"It is a scalable solution...The technical support team is fine."
"The most valuable features are being able to visualize the data in the diagrams and transform those diagrams into physical database deployments. These features help, specifically, to integrate the data. When the source data is accumulated and modeled, the target model is in erwin and it helps resolve the data integration patterns that are required to map the data to accommodate a model."
"The fitting model is very intuitive."
"It reduces monthly savings by hundreds of thousands of dollars. Think about a company like Costco and all of the points of sale systems in Costco, all of the systems, the applications, but if all the applications in Costco all had their own data model, trying to integrate those, upgrade them and manage their different versions of the same model throughout the store, is an absolute nightmare. It's phenomenally expensive. This helps reduce that cost significantly. I'm talking on the orders of hundreds of thousands of dollars."
"It has centralized storage so that a data model can be shared by different teams."
"The visual data models for helping to overcome data source complexity and enabling understanding and collaboration around maintenance and usage are excellent. A picture speaks 1,000 words. Seeing a picture that shows you how the data relates to each other helps you better understand what the data is and how to use it. Pairing that information with a dictionary, which has the definitions of the tables and columns or the entities and attributes, ensures that the users understand what the data is so that they can use it best and most successfully."
"It allows us to create logical data models. We can represent a database model in business terms, which is very useful for us."
"The most valuable feature is the physical or visual representation of the database, showing the tables, the columns, the foreign keys, and the ability to generate DDL, so you can physically implement databases."
"Automated document generation is a real time saver, no more cut and paste, no more keeping track of which diagrams are in which reports, no more last minute update panics. Just click a mouse and you've got an up to date report."
"There are a couple of things. Price is one thing, but we also like the scriptability of it. We got into scripting it and automating tasks with it, and it is super duper easy to do and helpful. The API has improved over the years. We automate everything, and I love the automation aspects of it."
"A feature I like most about Sparx Systems Enterprise Architect is its ease of use."
"We use it to develop and maintain the Enterprise Conceptual Model, migrated from erwin a couple of years ago."
"Its most valuable feature is the Zachman Framework."
"It is a very rich tool in terms of the functionality, and the types of diagrams, that you can create in this tool."
"The product offers very good support for all mainstream modeling notations and architectural frameworks."
"Its traversability is most valuable. I can use ArchiMate, and I can create a UML model. ArchiMate is for logical enterprise architecture, UML is for software engineering, and BPMN is for business processes. I can build it to have multiple models, and they are also traversable, which is not something that every tool allows. If there is a huge organization, you can segment it and have separate models for business technology or internal resource management system. You don't need to keep them in one model, and you can decide to segregate them."
"The navigation is a little bit of a challenge. It's painful. For example, if you've got a view open and you want to try to move from side to side, the standard today is being able to drag and drop left and right. You can't really do that in the model. Moving around the model is painful because it doesn't follow the Windows model today."
"I would like to see the reporting capabilities be more dynamic and more inclusive of information. The API is very sparsely understood by people across the user community."
"erwin is not as robust as a data warehousing project I've been on in the past."
"I would like to have more data sources from other, different vendors. In recent years, the vendor has reduced the number of data sources, and I would like to have more data sources for every brand. For example, with Oracle, I would like to have compatibility for many versions, including old ones, not just the most recent."
"I find the UI very clunky and very difficult to use. If I add columns to a table the whole workflow could be so much easier. I get frustrated using it. I've tried other tools. I've tried to get off of erwin a few times. I always come back to it because every tool has its own set of problems, and it seems like if I have to pick my poison, I stay with erwin. But so many things that are clunky with it."
"It does not have a cloud application."
"The only real complaint I have is the time it takes to do a database comparison on a large model. If they could speed that up, that would be the only thing I can think of that needs improvement."
"The erwin Data Modeler is quite complex to use."
"If you just want to create some diagrams with shapes and arrows, then use Visio."
"The UI is a little bit outdated. It should be more fresh and clean."
"I have found the solution is lacking options. The general usability needs improvement and more compliance to CML definitions."
"It took me a while to figure out how to use the report generation features effectively. So, it would be really nice if they had a way to make that a little bit more interactive and a little bit more straightforward."
"Weak in regards to data modelling. No logical or physical modelling or migration from conceptual to physical."
"The solution needs to offer better support for the mobile-based system. Right now, it's not working."
"The initial setup of the Sparx Systems Enterprise Architect It's very complicated. It's very difficult to start with the right templates because there are many possibilities. The deployment took approximately two days."
"The user interface is not so good. It's not easy for someone to use it at first. The product takes some getting used to."
More Sparx Systems Enterprise Architect Pricing and Cost Advice →
erwin Data Modeler by Quest is ranked 3rd in Enterprise Architecture Management with 37 reviews while Sparx Systems Enterprise Architect is ranked 2nd in Enterprise Architecture Management with 97 reviews. erwin Data Modeler by Quest is rated 8.6, while Sparx Systems Enterprise Architect is rated 8.0. The top reviewer of erwin Data Modeler by Quest writes "The product lets users import different types of models, but it is expensive, and the interface must be improved". On the other hand, the top reviewer of Sparx Systems Enterprise Architect writes "Easy to set up and had no issues with stability, but it's not a very friendly tool, and its database modeling and entity-relationship modeling functions need improvement". erwin Data Modeler by Quest is most compared with SAP PowerDesigner, IDERA ER/Studio, Lucidchart, Visio and AWS Well-Architected Tool, whereas Sparx Systems Enterprise Architect is most compared with Visual Paradigm, Visio, No Magic MagicDraw, LeanIX and iServer. See our Sparx Systems Enterprise Architect vs. erwin Data Modeler by Quest report.
See our list of best Enterprise Architecture Management vendors and best Business Process Design vendors.
We monitor all Enterprise Architecture Management reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
