We performed a comparison between erwin Data Modeler by Quest and erwin Evolve by Quest based on real PeerSpot user reviews.
Find out in this report how the two Enterprise Architecture Management solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."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."
"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 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."
"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."
"The ability to collaborate between different members across the organization is the most valuable feature. It gives us the ability to work on the same model, regardless of where we are physically."
"The most valuable features are the ability to reverse engineer and do model comparison. With the reverse engineering, I can understand the databases from third-party products. With the model comparison, I can track the differences between two versions of the same database."
"There is absolutely no problem with the stability."
"Drag-and-drop data modeling and reverse engineering out of databases are the most valuable features of erwin Data Modeler by Quest."
"One of the most valuable features is the website that sits on top of the database. There's a database of objects and how they are related, and you can make views and diagrams and visual elements out of that information on the website. The website is the part that is called Evolve and we use the Evolve Designer and publish the website out to our employees. They can click around and navigate and search, etc."
"Support for a broad range of data sources from relational to big data to the Cloud."
"The initial setup was really straightforward and the deployment was done within one day."
"I can send images in the PDF form, along with the relationships and the associations that are a very important part of what we do. It can show what is affected and what is impacted by a certain change in one area of the system architecture or enterprise architecture. I can very quickly draw those issues and topics to the fore."
"I really liked that it mapped out processes and was able to attach the data model to the appropriate process. You could map out the process, then when you got down to a specific couple of data elements, you could attach the table in the database that supported that process. You could connect it with erwin Data Modeler for that."
"Workgroup Repository collection of data models allows research across models without worry about platform incompatibilities and provides easy KPIs about corporate data assets."
"By placing the data and the metadata into a model, which is what the tool does, you gain the abilities for linkages between different objects in the model, linkages that you cannot get on paper or with Visio or PowerPoint. That is a huge discriminator."
"We can efficiently deploy business models into the databases and generate SQL scripts."
"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."
"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."
"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."
"It is not a very stable solution. I rate the stability five out of ten."
"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."
"I would like the solution to be more user-friendly to deploy."
"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."
"We are planning to move, in 2021, into their server version, where multiple data modelers can work at the same time and share their models. It has become a pain point to merge the models from individual desktops and get them into a single data model, when multiple data modelers are working on a particular project. It becomes a nightmare for the senior data modeler to bring them together, especially when it comes to recreating them when you want to merge them."
"Add some ability to do conditional Visualization on the models and in reports (some ideas) – maybe as a specialized Theme or Diagram or Display."
"I would like it to be easier to make changes and then deploy them into production, especially when you have multiple web servers or front-ends. It would be nice to make a change and then have it propagate to the production servers in a more automated fashion."
"The solution's integration capabilities with other tools in our system has not been all that well done. We have people who use ARIS, who use System Architect and, of course, Visio. erwin has very limited ways to import and export from those kinds of tools. It's not a very easy thing to do."
"I would like to see an improvement in the output of the solution."
"What they need to do is to consolidate more of their products. For example, I was just looking and I couldn't figure out what erwin DT is. It's on the website but it would help if they could put information together and make it more clear as to what products they have and how they work with other things."
"The solution needs to focus on allowing for more integrations."
"They have improved the search engine a little bit but it can always be improved more. The more data you put inside it, the more you want to use it."
"With the Excel importing, the "up to date" part is the challenge. If we had a real-time integration, we could keep things up to date for whatever kinds of change points we had. With Excel, it is more that you have to export from one system then import it to another, so it's better for data that doesn't change that often."
erwin Data Modeler by Quest is ranked 3rd in Enterprise Architecture Management with 37 reviews while erwin Evolve by Quest is ranked 9th in Enterprise Architecture Management with 19 reviews. erwin Data Modeler by Quest is rated 8.6, while erwin Evolve by Quest 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 erwin Evolve by Quest writes "Enables us to present data and objects visually, in diagrams, and to make them available via the web. Also enables web-based editing of data". erwin Data Modeler by Quest is most compared with SAP PowerDesigner, IDERA ER/Studio, Visio, Lucidchart and Avolution ABACUS, whereas erwin Evolve by Quest is most compared with Sparx Systems Enterprise Architect, LeanIX, IDERA ER/Studio, SAP PowerDesigner and Avolution ABACUS. See our erwin Data Modeler by Quest vs. erwin Evolve by Quest report.
See our list of best Enterprise Architecture Management vendors and best Business Process Design vendors.
We monitor all Enterprise Architecture Management 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.
