We performed a comparison between erwin Data Modeler by Quest and Visio 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 can create mappings in erwin and possibly data dictionaries."
"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."
"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."
"The generation of DDL saved us having to write the steps by hand. You still had to go in and make some minor modifications to make it deployable to the database system. However, for the data lineage, it is very valuable for tracing our use of data, especially personal confidential data through different systems."
"It is a scalable solution...The technical support team is fine."
"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."
"It reduces monthly savings by hundreds of thousands of dollars. Think about a company like Costco and all of the points of sale systems in Costco, all of the systems, the applications, but if all the applications in Costco all had their own data model, trying to integrate those, upgrade them and manage their different versions of the same model throughout the store, is an absolute nightmare. It's phenomenally expensive. This helps reduce that cost significantly. I'm talking on the orders of hundreds of thousands of dollars."
"The data lineage feature is very valuable."
"The ability to visualize a workflow is certainly an advantage over just tracking a process in something like Excel."
"The fact that it's on-premises allows you to get fantastic speed. It's got a faster response rate, it doesn't lag, and it doesn't have any latency when you're working on it."
"The most valuable feature of this product is its versatility."
"What I like best about Visio is that it's flexible. Sometimes, if I need to draw quickly, I use Microsoft PowerPoint, but if I need icons, which Visio has, I use Visio. I also like that the solution gives me a much more powerful range of options."
"The interface of the solution is very good. It's easy to navigate."
"The primary functionality revolves around the creation of flow diagrams and diverse Building Information Modeling (BIM) using contemporary and pre-established notations. In my perspective, these ready-made notations prove highly beneficial. Despite being a compact tool, it is effective for tasks such as drawing organizational charts, making it a straightforward and uncomplicated tool."
"Visio is outstanding because it has features that are useful for project management."
"The most valuable feature is how easy it is to use."
"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."
"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."
"We can only get licenses through partners."
"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."
"I am not so happy with its speed. Sometimes, it can have problems with connections."
"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."
"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."
"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 is a visualization tool, so database visualization is pretty static in it. They haven't moved the ERDs very well. They haven't adopted any real visualization like what you have in Hackolade for JSON or other data patterns. It has none of that. If you go onto broader patterns, you can actually label and integrate with a data set, if you want, for Visio, but it's very clunky and very difficult for me to assign that to another user. I can't assign it to a junior or a documenter. They really haven't cleaned up and made their tools simpler to use when linking to data, which is primarily what you're trying to do."
"Indeed, Visio should progress beyond its current stage of solely drawing diagrams and transition into a more advanced phase, possibly integrating with different packages or aligning with Microsoft's offerings. It could potentially evolve into a comprehensive business process management solution, comparable to tools like Addis or Signavio, thereby competing in the realm of process management tools. It might be advantageous to explore functionalities such as process simulations or benchmarking, introducing simulators to discern potential bottlenecks or errors within complex flow diagrams. This addition would prove valuable for business analysts seeking insights into the intricacies of their diagrams, aligning with the evolving trends observed over the past six years."
"The database modeling has deteriorated significantly in the more current versions."
"Extremely large complex drawings need to be saved on the cloud for access."
"There are some issues in Visio with the connectors, and it gets tricky when you want to connect objects with each other."
"The product only functions well professionally, with adding additional software for configuration."
"There are a lot of patches that sometimes change how one version will interact compared to another."
"There should be more items available from a variety of other products that can be integrated."
erwin Data Modeler by Quest is ranked 9th in Business Process Design with 37 reviews while Visio is ranked 1st in Business Process Design with 100 reviews. erwin Data Modeler by Quest is rated 8.6, while Visio is rated 7.8. 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 Visio writes "A software for drawing a variety of diagrams which include flowcharts, org charts, building plans, floor plans, data flow diagrams". erwin Data Modeler by Quest is most compared with SAP PowerDesigner, IDERA ER/Studio, Lucidchart, Sparx Systems Enterprise Architect and AWS Well-Architected Tool, whereas Visio is most compared with Sparx Systems Enterprise Architect, Bizagi, Visual Paradigm, IBM Blueworks Live and ARIS BPA. See our Visio 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.
