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."The solution is good for organizing the data and the scripting part is very powerful. It's easy to create technical scripts for models."
"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."
"The data lineage feature is very 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."
"The product lets us import different types of models from various databases."
"The visual data models for helping to overcome data source complexity and enabling understanding and collaboration around maintenance and usage are excellent. A picture speaks 1,000 words. Seeing a picture that shows you how the data relates to each other helps you better understand what the data is and how to use it. Pairing that information with a dictionary, which has the definitions of the tables and columns or the entities and attributes, ensures that the users understand what the data is so that they can use it best and most successfully."
"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."
"We can create mappings in erwin and possibly data dictionaries."
"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."
"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."
"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."
"Forward and reverse engineering were valuable features."
"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."
"The ability to share and collaborate on the solution is its most valuable feature."
"The feature that stands out for me is the ease of configuring objects and the screens to show them. It's really easy to add a new type of object in this reference. Creating a new type of object, using it, and evolving it a little bit in terms of what we can document about it are the main features that made us decide to use this provider."
"We can efficiently deploy business models into the databases and generate SQL scripts."
"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."
"I would like the solution to be more user-friendly to deploy."
"The reverse engineering in Oracle Databases needs improvement, as there are issues."
"I would like to see the ability to support more NoSQL platforms more quickly. In addition, enhancing the graphics to render more quickly would be beneficial for any user."
"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."
"The solution's reporting side needs to be improved."
"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 to see an improvement in the output of the solution."
"The solution needs to focus on allowing for more integrations."
"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."
"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."
"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."
"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."
"They need to develop Evolve's user experience. For example, MEGA has a useful client view that helps with impact analysis. MEGA provides information about the processes, services, infrastructure, and portfolio of applications in one central view. It lets you see the periphery and relationships among components. This view is impressive, and Evolve doesn't have it."
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.