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."Any tool will do diagramming but I think the ability to put the stuff up in a graphical fashion, then think about it, and keep things consistent is what's valuable about it. It's too easy when you're using other methods to not have naming consistent standards and column consistent definitions, et cetera."
"The ability to collaborate between different members across the organization is the most valuable feature. It gives us the ability to work on the same model, regardless of where we are physically."
"Another feature of erwin is that it can help you enforce your naming standards. It has little modules that you can set up and, as you're building the data model, it's ensuring that they conform to the naming standards that you've developed."
"The product lets us import different types of models from various databases."
"Being able to point it to a database and then pull the metadata is a valuable feature. Another valuable feature is being able to rearrange the model so that we can display it to users. We are able to divide the information into subject areas, and we can divide the data landscape into smaller chunks, which makes it easier to understand. If you had 14 subject areas, 1,000 entities, and 6,000 columns, you can't quite understand it all at once. So, being able to have the same underlying model but only display portions of it at a time is extremely useful."
"It's important to create standard templates — Erwin is good at that — and you can customize them. You can create a standard template so that your models have the same look and feel. And then, anyone using the tool is using the same font and the same general layout. erwin's very good at helping enforce that."
"Forward engineering, DDL generation, reverse engineering, and reporting are the most valuable features of the solution."
"We find that its ability to generate database code from a model for a wide array of data sources cuts development time. The ability to create one model in your design phase and then have it generate DDL code for Oracle or Teradata, or whichever environment you need is really nice. It's not only nice but it also saves man-hours of time. You would have to take your design and just type in manually. It has to take days off out of the work."
"I like that there is support for software patterns."
"There are a lot of features in Enterprise Architect. It allows us to take on a lot of tasks."
"We use it to develop and maintain the Enterprise Conceptual Model, migrated from erwin a couple of years ago."
"The initial setup is easy."
"It's a stable and scalable solution. I like that it's similar to Rational Rose."
"It is a very flexible product. It can do a lot. It is also a reliable product."
"I have found the Meta Model tuning feature useful as it provides me with an overview of all my work needs."
"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."
"I am not so happy with its speed. Sometimes, it can have problems with connections."
"This is a very complex product."
"erwin is not as robust as a data warehousing project I've been on in the past."
"I would like to see the ability to support more NoSQL platforms more quickly. In addition, enhancing the graphics to render more quickly would be beneficial for any user."
"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."
"The solution's reporting side needs to be improved."
"The report generation has room for improvement. I think it was version 8 where you had to use Crystal Reports, and it was so painful that the company I was with just stayed on version 7 until version 9 came out and they restored the data browser. That's better than it was, but it's still a little cumbersome. For example, you run it in erwin, then export it out to Excel, and then you have to do a lot of cosmetic modification. If you discover that you missed a column, then you would have to rerun the whole thing. Sometimes what you would do is just go ahead and fix it in the report, then you have to remember to go back and fix it in the model. Therefore, I think the report generation still could use some work."
"It would be nice to have it on the Linux platform, not just Windows. If they can support Linux, there would be a huge market for it."
"For data modeling, it is not very mature when comparing with other data modeling tools."
"Even if there are web-based tools in the Enterprise Architecture tool ecosystem (like Prolaborate), the main modeling application is still a fat client application."
"Weak in regards to data modelling. No logical or physical modelling or migration from conceptual to physical."
"The UI is a little bit outdated. It should be more fresh and clean."
"I struggled with most of the features for this tool, as did the rest of our architecture team."
"This solution has some limitations from a business perspective."
"It can be improved in the area of shared documentation. The idea is that the architecture tool can call back to an enterprise asset, pull that information, and link that as a sub-artifact."
"One room for improvement in Sparx Systems Enterprise Architect is that it's not very friendly. Another room for improvement in the tool is that it doesn't enable you to import the metadata from a database very easily, so reverse engineering of a database was very difficult. Its database modeling and entity-relationship modeling functions need improvement."
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, Lucidchart 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.
