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."Another feature of erwin is that it can help you enforce your naming standards. It has little modules that you can set up and, as you're building the data model, it's ensuring that they conform to the naming standards that you've developed."
"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."
"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 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 allows us to create logical data models. We can represent a database model in business terms, which is very useful for us."
"We use the Forward and Reverse Engineering tools to help us speed things up and create things that would have to be done otherwise by hand. E.g., getting a database into a data model format or vice versa."
"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."
"We can create mappings in erwin and possibly data dictionaries."
"The most valuable features are that the user experience is simple, and it's customizable."
"The most valuable feature is that it is integrated with other tools in the Microsoft Office suite, as well as at the backend with products like SharePoint and Microsoft Teams."
"The most valuable feature of this product is its versatility."
"It is stable. I have never experienced any issues."
"The solution is very user-friendly."
"The Data Objects are hyperlinked to the Standard Operating Procedures, Letters, and Forms."
"I think the best part of Visio is that you can import drawings very well into Microsoft Word. For example, if you put the Visio drawing into Word, you can double click on it and it opens in Visio. It is a very useful feature and something which I miss switching to Enterprise Architect. In Enterprise Architect, if I import a drawing into Word it does not open the diagram in Enterprise Architect. This is one of the strongest features and the ability to create your own stencils."
"The solution makes it very easy to make exciting pictures and designs. Everything is very intuitive and simple to figure out."
"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."
"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 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."
"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."
"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."
"I would like the solution to be more user-friendly to deploy."
"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."
"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."
"Lacks stencils for new technologies in the solution."
"It's not the easiest software to use. It's not user-friendly out-of-the-box."
"It would be nice if there is a database behind it. We have looked into this functionality, but all of the other solutions that have a database are very locked down, and you have to use them their way. You can't define your own stuff. For example, we have a system X, and I want to define system X myself and have it available. If I am ever going to make a change to system X, I want to pull up all the drawings that are associated with system X. I want to be able to search and pull all those drawings. Visio should have the ability to capture metrics associated with each step in the process. For example, based on a specific time, I should be able to link the data to a spreadsheet, which is kind of like the data analysis on the process."
"The solution should be included in Microsoft Office 365. For some reason, it's not. It should be bundled in with everything else."
"One issue I've noticed is that when working on a shared video link with a friend for Visio, there can be a delay in changes reflecting on their screen after I've made them. This also occurs when we're working on the same document. It would be beneficial if changes could be reflected in real-time. Additionally, I've experienced some text size issues with the flow task feature. Sometimes when I enter text, it appears very small, and increasing the size causes it to extend beyond the diagram, creating formatting issues. It would be helpful if these text and formatting issues could be addressed."
"I think that it feels a bit outside with respect to the icons that are available."
"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 auto-routing feature could be better."
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 101 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.
