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."Drag-and-drop data modeling and reverse engineering out of databases are the most valuable features of erwin Data Modeler by Quest."
"We use the macros with naming standards patterns, domains, datatypes, and some common attributes. As far as other automations, a feature of the Bulk Editor is mass updates. When it sees something is nonstandard or inaccurate, it will export the better data out. Then, I can easily see which entities and attributes are not inline or standard. I can easily make changes to what was uploaded to the Bulk Editor. When taking on a new project, it can save you about a half a day on a big project across an entire team."
"The data lineage feature is very valuable."
"It supports a wide variety of databases, including the latest ones. We have chosen to go for a cloud-based database, and it supports that, which is very useful."
"It is a scalable solution...The technical support team is fine."
"We had some data integration projects, where we needed to integrate it for about 100 databases. Doing that manually is crazy; we can't do that. With erwin, it was much easier to identify which tables and columns could be used for the integration. That means a lot in terms of time and effort as well as my image to the customer, because they can see that we are providing value in a very short time."
"The logical model gives developers, as well as the data modelers, an understanding of exactly how each object interacts with the others, whether a one-to-many, many-to-many, many-to-one, etc."
"The solution's ability to compare and synchronize data sources with data models is fantastic. We use it for that on a regular basis to make sure that changes haven't been made to the database outside of the modeling process. I can take existing databases and reverse engineer them and understand their structure within 15 minutes. If I didn't have Data Modeler it would take hours. It increases our productivity and helps in understanding our legacy application."
"Large variety of profiles and frameworks available out-of-the-box without the need for customization."
"Artifact templates are most valuable."
"The profiles and ready-made templates are an extremely helpful feature. This is one of the biggest features that I find very useful in Sparx."
"We use it to develop and maintain the Enterprise Conceptual Model, migrated from erwin a couple of years ago."
"The features I find most valuable is the ability to create a document and then put it into a OneCare artifact."
"Modeling is a part of my work, and it has a lot of standard modeling languages. It is quite wide, and a lot is possible in it. We are not programming it ourselves, but if you are into programming and developing software yourself, you can go further and do a lot with Sparx. You can work from the framework and go into the details. With this solution, you get a lot of value at a low cost. It is also quite intuitive in terms of use. I like the use of it."
"We can easily use it with our new customers."
"It has led some teams to do better code reviews - to be less focussed on coding conventions (syntax) and more focussed on the semantics because of the abstraction level clear design affords."
"I would like to see more support for working with the big-data world. There are so many new databases evolving and it's very hard for them to keep up with all of the new technologies. It would be good if they were able to dynamically support big-data platforms, other than Hive and Teradata."
"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."
"I am not so happy with its speed. Sometimes, it can have problems with connections."
"Some Source official systems give us DDLs to work with and they have contents not required to be part of the DDL before we reverse engineer in the erwin DM. Therefore, we manually make changes to those scripts and edit them, then reverse-engineer within the tool. So, it does take some time to edit these DDL scripts generated by the source operational systems. What I would suggest: It would be helpful if there were a place within the erwin tool to import the file and automatically eliminate all the unnecessary lines of code, and just have the clean code built-in to generate the table/data model."
"The solution's reporting side needs to be improved."
"In terms of improvements, support could have been better in terms of installation, especially of workgroups. We struggled quite a bit to get it up and running. Collaboration could have been better from an installation perspective, but it is trivial as compared to what we use it for. Other than that, I don't have much feedback. It works pretty well, and the fact that we've been using it for more than a decade shows that it is quite solid."
"erwin is not as robust as a data warehousing project I've been on in the past."
"The erwin ETL functionality has room for improvement when it comes to mapping databases with a classic entity-relationship model to a data warehouse model."
"I think that collaboration can be better."
"The window froze for five or ten seconds. You can click and click again and it takes a second to come up. It might have been specific to a version."
"Inconsistent UI elements must be tidied up with the toolbox gaps removed."
"It would be great if we could decrease the use of different parts of the Toolbox."
"The automatic creation of reports based on the model elements could be improved."
"The reporting needs improvement."
"When many users are accessing the system at the same time, Sparx slows down. It can't easily support a large team."
"In general, we now have a problem with Sparx Enterprise Architect because many analysts think it's too complicated to use in a giant environment."
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, Visio, Lucidchart 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.
