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 allows us to create logical data models. We can represent a database model in business terms, which is very useful for us."
"The product lets us import different types of models from various databases."
"It's important to create standard templates — Erwin is good at that — and you can customize them. You can create a standard template so that your models have the same look and feel. And then, anyone using the tool is using the same font and the same general layout. erwin's very good at helping enforce that."
"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."
"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 data lineage feature is very valuable."
"The solution is excellent in providing a visual representation of a database and can generate DDL for implementing changes. We use DDL for logical purposes to review with business people, ensuring they have the required fields for processing. We also use it as a data dictionary for the physical data model to understand all the purposes of the terms. This helps us map the logical and physical terms with the business definition to understand our data."
"It provides flexibility with the code. You can change the code as you want. Basically, you can change SQL based on what's best for your project."
"The initial setup was really straightforward and the deployment was done within one day."
"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."
"I have not seen capabilities for web-sharing and interaction with the architecture from any other supplier. It's a great capability..."
"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."
"Support for a broad range of data sources from relational to big data to the Cloud."
"There is a model behind it. It's really nice that the Evolve front-end, as it builds a website, keeps those relationships in mind. You can even go to a procedure and see all the applications that are related to it. Then you can go into that application and see all the standard operating procedures that that application is a part of. It's just very connected."
"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."
"We use erwin Evolve to publish to the website. This allows us to enable publishing our website using parameterisation features. In a very fast, quick way, we can publish a table or chart onto a website."
"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."
"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."
"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."
"I would like to see improved reporting and, potentially, dashboards built on top of that. Right now, it's a little manual. More automated reporting and dashboard views would help because currently you have to push things out to a spreadsheet, or to HTML, and there aren't many other options that I know of. I would like to be able to produce graphs and additional things right in the tool, instead of having to export the data somewhere else."
"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."
"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 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."
"The way that we are using it for application management, we have several KPIs. We want to follow and monitor them regarding a number of solutions. We cannot calculate this today. We would like real-time calculations along with the KPIs in order to improve the user experience. We would like the tool to be able to display this, not only as signals, but as charts."
"The solution needs to focus on allowing for more integrations."
"I feel that the UML drawing capability needs to be improved."
"It could have had a more streamlined navigation. It seemed that when you went to the explorer panel, there were just so many different ways of doing the work that I could not remember, "How did I do this? How did I get to that point in that model to get back to it?" If I wanted to build a new one, where do I start? It just seemed like there was such a smorgasbord of ways of doing it that it was just overwhelming."
"Add some ability to do conditional Visualization on the models and in reports (some ideas) – maybe as a specialized Theme or Diagram or Display."
"There might be improvement required to better support some of the MPP databases for non-relational data structures and NoSQL databases."
"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."
"Evolve is primarily focused on the entity's licenses diagrams, but it would be nice if erwin could integrate case development, so that it shows the ER diagram plus certain inputs on the use cases and how the data is used. That deviates somewhat from the overall scope, so maybe they could call it a different product."
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, Lucidchart, Visio and BiZZdesign HoriZZon, whereas erwin Evolve by Quest is most compared with Sparx Systems Enterprise Architect, LeanIX, SAP PowerDesigner, IDERA ER/Studio 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.
