We performed a comparison between erwin Data Modeler by Quest and UNICOM 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."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."
"Forward engineering, DDL generation, reverse engineering, and reporting are the most valuable features of the solution."
"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."
"It supports a wide variety of databases, including the latest ones. We have chosen to go for a cloud-based database, and it supports that, which is very useful."
"It is a scalable solution...The technical support team is fine."
"Drag-and-drop data modeling and reverse engineering out of databases are the most valuable features of erwin Data Modeler by Quest."
"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."
"It has centralized storage so that a data model can be shared by different teams."
"It has good end-to-end metamodel interrelationships."
"It is useful for creating build-outs and architecture views and for publishing reports and stuff like that for different programs."
"erwin generally fails to successfully reverse engineer our Oracle Databases into erwin data models. The way that they are engineered on our side, the syntax is correct from an Oracle perspective, but it seems to be very difficult for erwin to interpret. What I end up doing is using Oracle Data Modeler to reverse engineer into the Oracle data model, then forward engineer the DDL into an Oracle syntax, and importing that DDL into erwin in order to successfully bring in most of the information from our physical data models. That is a bit of a challenge."
"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."
"I would like to see more support for working with the big-data world. There are so many new databases evolving and it's very hard for them to keep up with all of the new technologies. It would be good if they were able to dynamically support big-data platforms, other than Hive and Teradata."
"Some Source official systems give us DDLs to work with and they have contents not required to be part of the DDL before we reverse engineer in the erwin DM. Therefore, we manually make changes to those scripts and edit them, then reverse-engineer within the tool. So, it does take some time to edit these DDL scripts generated by the source operational systems. What I would suggest: It would be helpful if there were a place within the erwin tool to import the file and automatically eliminate all the unnecessary lines of code, and just have the clean code built-in to generate the table/data model."
"The erwin Data Modeler is quite complex to use."
"The interface must be improved."
"It is not a very stable solution. I rate the stability five out of ten."
"I don't use the tool or know a lot. It is going to have some shortcomings. When it comes down to publishing, we just found out this week that they actually have a publisher add-on. So, what we were trying to publish was not giving a detailed report about the architecture, views, etc. I just wish they had sent these to UNICOM and contacted them about add-on features for the publishing part of the tool."
"They need to add reports that show the enterprise architecture perspectives, and the dashboards should be comfortable for the senior enterprise architects so that they can view the complete landscape."
Earn 20 points
erwin Data Modeler by Quest is ranked 3rd in Enterprise Architecture Management with 37 reviews while UNICOM System Architect is ranked 25th in Enterprise Architecture Management. erwin Data Modeler by Quest is rated 8.6, while UNICOM System Architect is rated 6.0. 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 UNICOM System Architect writes "Useful for creating build-outs and architecture views, but requires a publisher add-on for some detailed reports". erwin Data Modeler by Quest is most compared with SAP PowerDesigner, IDERA ER/Studio, Lucidchart, Visio and Sparx Systems Enterprise Architect, whereas UNICOM System Architect is most compared with Sparx Systems Enterprise Architect. See our UNICOM 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.
