We performed a comparison between erwin Data Modeler by Quest and Visual Paradigm based on real PeerSpot user reviews.
Find out in this report how the two Business Process Design solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."When you're getting down to the database level, where you're building a design and you're creating DDL out of it, or you're going in the other direction where you're reaching into system catalogs and bringing things back, that starts to really require specialization. Visio isn't going to reverse-engineer that for you. Those features in erwin are valuable."
"It is a scalable solution...The technical support team is fine."
"The principal feature that I liked is that the solution has a very graphic interface."
"The data lineage feature is very valuable."
"What has been useful, I have been able to reverse engineer our existing data models to document explicitly referential integrity relationships, primary/foreign keys in the model, and create ERDs that are subject area-based which our clients can use when working with our databases. The reality is that our databases are not explicitly documented in the DDL with primary/foreign key relationships. You can't look at the DDL and explicitly understand the primary/foreign key relationships that exist between our tables, so the referential integrity is not easily understood. erwin has allowed me to explicitly document that and create ERDs. This has made it easier for our clients to consume our databases for their own purposes."
"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."
"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."
"It allows us to create logical data models. We can represent a database model in business terms, which is very useful for us."
"The solution is very user-friendly. It's easy to just open it and start working."
"I like the fact that this solution is complete."
"It is easy and intuitive to use, not excessively rigid, and quite flexible."
"Some of the most valuable features of this process modeling tool are process simulation and process animation."
"It is a scalable solution since it can be used at an individual level as well as for enterprise-sized businesses."
"What I found most valuable in Visual Paradigm is diagramming. I had a great user experience as diagramming in the tool is easy and convenient, even for complex diagrams or models. Visual Paradigm is the perfect tool for me, and I prefer it over Sparx Systems Enterprise Architect. Visual Paradigm is better for collaboration if you consider, for example, versioning, so this is another valuable tool feature that's simple and embedded in the solution. In Visual Paradigm, it's also easy to set up the project with team members and collaborate, and it's also a pro of the tool."
"The initial setup is straightforward."
"Stable design software with multiple functions and features. It's simple to install and easy to use."
"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."
"Complete Compare is set up only to compare properties that are of interest to us, but some of the differences cannot be brought over from one version of the model to another. This is despite the fact that we are clicking to bring objects from one place to another. Therefore, it's hard to tell at times if Complete Compare is working as intended without having to manually go into the details and check everything. If it could be redesigned to a degree where it is easier to use when we bring things over from one site to another and be sure that it's been done correctly, that would be nice to have. We would probably use the tool more often if the Complete Compare were easier to use."
"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 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."
"The Bulk Editor needs improvement. If you had something that was a local model to your local machine, you could connect to the API, then it would write directly into the repository. However, when you have something that is on the centralized server, that functionality did not work. Then, you had to export out to a CSV and upload up to the repository. It would have been nice to be able to do the direct API without having that whole download and upload thing. Maybe I didn't figure it out, but I'm pretty sure that didn't work when it was a model that sat on a centralized repository."
"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."
"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."
"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."
"I was looking to generate code from the diagrams, but it was not totally clear how to do it."
"Visual Paradigm could improve many aspects. The performance could be better because it can be low. When we have large and complicated models, it has a low speed and many bugs. Sometimes the solution stops and you have to restart Microsoft Windows on your PC. The larger database modeling cannot be done properly, I have to use another solution called SAP PowerDesigner."
"I would like to see something for visualizing innovation work maps."
"The solution is not user-friendly. It uses a lot of memory and CPU. You have to have a good computer to use it."
"There are some connectivity issues that crop up rarely when used with SQL Server."
"The solution can be heavy on resource usage."
"In terms of room for improvement in Visual Paradigm, I tried looking for one. I'm pleased with the tool, but it would be great if you could integrate Visual Paradigm with more tools. For example, when moving from Visual Paradigm to another tool, such as Sparx Systems Enterprise Architect, the process could be improved a bit. Still, I wonder if it's not limited by the standards Visual Paradigm follows, such as XMI files. It could be connected to limitations related to the standards rather than a tool limitation. When you move projects from Visual Paradigm into Sparx Systems Enterprise Architect via XMI files, you lose all your notes from the elements, so this is an area for improvement in Visual Paradigm. TOGAF support is an additional feature I'd like to see in the next release of Visual Paradigm. I'd also like the tool to have ArchiMate support. If both TOGAF and ArchiMate could be supported in Visual Paradigm and made part of a lower level of licensing or cheaper licensing models, that would be best for me."
"More flexibility when choosing the type of diagram would be nice."
erwin Data Modeler by Quest is ranked 9th in Business Process Design with 37 reviews while Visual Paradigm is ranked 7th in Business Process Design with 25 reviews. erwin Data Modeler by Quest is rated 8.6, while Visual Paradigm 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 Visual Paradigm writes "Very flexible and easy to use with a good pricing model". erwin Data Modeler by Quest is most compared with SAP PowerDesigner, IDERA ER/Studio, Lucidchart, Visio and No Magic MagicDraw, whereas Visual Paradigm is most compared with Sparx Systems Enterprise Architect, Visio, Lucidchart, Bizagi and Camunda. See our Visual Paradigm vs. erwin Data Modeler by Quest report.
See our list of best Business Process Design vendors.
We monitor all Business Process Design 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.