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."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."
"We can create mappings in erwin and possibly data dictionaries."
"It allows us to create logical data models. We can represent a database model in business terms, which is very useful for us."
"It has centralized storage so that a data model can be shared by different teams."
"The solution’s code generation ensures accurate engineering of data sources, as there is no development time. Code doesn't even have to be reviewed. We have been using this solution for so long and all the code which has been generated is accurate with the requirements. Once we generate the DDLs out of the erwin tools, the development team does a quick review of the script line by line. They will just be running the script on the database and looking into other requirements, such as the index. So, there is less effort from development side to create tables or build a database."
"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."
"Drag-and-drop data modeling and reverse engineering out of databases are the most valuable features of erwin Data Modeler by Quest."
"The product allows us to reuse entities and attributes."
"It is easy and intuitive to use, not excessively rigid, and quite flexible."
"It is a scalable solution since it can be used at an individual level as well as for enterprise-sized businesses."
"It is a scalable solution...The initial setup was straightforward."
"I like the fact that this solution is complete."
"The solution is the best application for data modeling. It helps to architect business processes. Its best features are pricing and functionality."
"Some of the most valuable features of this process modeling tool are process simulation and process animation."
"It is easy-to-use and it helps understand its data modeling structure through the intuitive user interface."
"Stable design software with multiple functions and features. It's simple to install and easy to use."
"In terms of new features, it would be great to have a cloud base. We should be able to put it on the cloud for better collaboration and data models sharing."
"One of the things I've been talking to the erwin team about through the years is that every data model should have the ability to be multi-language... When I was working at Honda, it became very difficult to work with the Japanese teams using just one model. You can have two models, one in English and one in Japanese, but that means you have to keep the updates back and forth, and that always increases the risk of something not being updated."
"erwin generally fails to successfully reverse engineer our Oracle Databases into erwin data models. The way that they are engineered on our side, the syntax is correct from an Oracle perspective, but it seems to be very difficult for erwin to interpret. What I end up doing is using Oracle Data Modeler to reverse engineer into the Oracle data model, then forward engineer the DDL into an Oracle syntax, and importing that DDL into erwin in order to successfully bring in most of the information from our physical data models. That is a bit of a challenge."
"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."
"The modeling product itself is far and above anything else that I've seen on the market. There are certain inconsistencies when it comes to keeping up with other platforms' databases in the reverse-engineering process. It should also support more database platforms."
"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 interface must be improved."
"The product's versioning capability needs improvement."
"Visual Paradigm's initial deployment was difficult since we did it for the first time. It is challenging to learn to use the product."
"Visual Paradigm is much better now. But each project has its own challenges, which is why I'm exploring different tools for my new projects. For instance, designing reports can be tough, especially with the costly intervention of professional services from vendors."
"The solution's technical support can be improved and accessible for our company location since Visual Paradigm follows a remote support model with some challenges."
"I would like to see the ability to easily export to groupware, such as Atlassian Confluence."
"From time to time, we experience some troubles when we work as teams."
"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."
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.
