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."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."
"The product allows us to reuse entities and attributes."
"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."
"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."
"It allows us to create logical data models. We can represent a database model in business terms, which is very useful for us."
"We can create mappings in erwin and possibly data dictionaries."
"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."
"It's a safeguard for me because I'm always concerned that somebody is free handing it and will forget a key coming from the parent. The migrating keys are a great feature. Identifying relationships, non-identifying relationships, and being visually right there to understand the differences are great features. erwin is key to being able to visually understand whatever the customer is requesting. They'll give you words on a paper, but once they can actually view it as a picture, it really comes to life. The data comes to life to where they understand exactly what they're asking for."
"Stable design software with multiple functions and features. It's simple to install and easy to use."
"The initial setup is straightforward."
"What I like best about Visual Paradigm is its simple GUI, especially since I'm a new user. In my two years of experience with this tool, I didn't find it complex because I was able to learn how to use it via YouTube videos. Visual Paradigm is enough for me. I also find the bridging feature in the tool valuable."
"I like the fact that this solution is complete."
"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 most valuable feature of the Visual Paradigm that I use is process modeling. Additionally, the solution has a complete set of features."
"Visual Paradigm is super user-friendly, especially for new team members. I always have them start with it because the interface is so simple to pick up. They usually spend about six months to a year using only Visual Paradigm before moving on to other tools. We also use the cloud repository for collaborative work, but I've had some trouble with code reviewing and limitations. Sometimes, customers even request the source file or exported XML because it's easier for them to access and review."
"The initial setup is extremely straightforward."
"It does not have a cloud application."
"The solution's reporting side needs to be improved."
"I would like the solution to be more user-friendly to deploy."
"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 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."
"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 still use Visio for conceptual modeling, and that's mainly because it is easier to change things, and you can relax some of the rules. DM's eventual target is a database, which means you actually have to dot all the Is and cross all the Ts, but in a conceptual model, you don't often know what you're working with. So, that's probably a constraint with erwin. They have made it a lot easier, and they've done a lot, but there is probably still room for improvement in terms of the ease of presentation back to the business. I'm comparing it with something like Visio where you can change colors on a box, change the text color and that sort of stuff, and change the lines. Such things are a whole lot easier in Visio, but once you get a theme organized in erwin, you can apply that theme to all of the objects. So, it becomes easier, but you do have to set up that theme."
"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."
"From time to time, we experience some troubles when we work as teams."
"I would like to see something for visualizing innovation work maps."
"The solution can be heavy on resource usage."
"The solution could be more compatible with other products in the future."
"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."
"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."
"There are some connectivity issues that crop up rarely when used with SQL Server."
"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."
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, Visio, Lucidchart 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.
