We performed a comparison between erwin Data Modeler by Quest and IBM Rational System Architect 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."They have a lot of features and the most up-to-date technology integration, which I haven't seen in other products."
"We can create mappings in erwin and possibly data dictionaries."
"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."
"Any tool will do diagramming but I think the ability to put the stuff up in a graphical fashion, then think about it, and keep things consistent is what's valuable about it. It's too easy when you're using other methods to not have naming consistent standards and column consistent definitions, et cetera."
"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 modeling portion of the tool is the most valuable. There are some notes, naming standards, and other functions that we use as well. There's a whole boatload of functionality in this thing and we use maybe 10% of it. It seems to be pretty common that not all the functionality is fully utilized. But it's just got gobs and gobs of stuff that you can implement if you so choose to."
"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 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 user interface is good. It's both clear and comprehensible. It's easy to work with."
"There are a lot of features I find valuable, but I think that the metamodel customization is one of the best features that the solution offers."
"The solution is pretty stable."
"We have seen ROI with this solution over the years that we have used it."
"The erwin Data Modeler is quite complex 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."
"There is a lack of local support in the China region."
"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."
"The interface must be improved."
"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."
"I am not so happy with its speed. Sometimes, it can have problems with connections."
"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."
"The solution needs to better integrate with other products, like Microsoft."
"The reverse engineering of the database is already there, but in the next release I would like to see some pilot supplied with the solution in order to address any database."
"This solution can be more user-friendly and easier to use, with better dashboards."
"There needs to be more information at the outset about how to use the solution and how to deploy it. The deployment process needs improvement."
Earn 20 points
erwin Data Modeler by Quest is ranked 3rd in Enterprise Architecture Management with 37 reviews while IBM Rational System Architect is ranked 21st in Enterprise Architecture Management. erwin Data Modeler by Quest is rated 8.6, while IBM Rational System Architect is rated 7.4. 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 IBM Rational System Architect writes "Modeling is useful, but many features need improvement and technical support is lacking". erwin Data Modeler by Quest is most compared with SAP PowerDesigner, IDERA ER/Studio, Lucidchart, Visio and Sparx Systems Enterprise Architect, whereas IBM Rational System Architect is most compared with Sparx Systems Enterprise Architect. See our IBM Rational System Architect vs. erwin Data Modeler by Quest report.
See our list of best Enterprise Architecture Management 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.