We performed a comparison between erwin Data Modeler by Quest and MEGA HOPEX 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 fitting model is very intuitive."
"The logical model gives developers, as well as the data modelers, an understanding of exactly how each object interacts with the others, whether a one-to-many, many-to-many, many-to-one, etc."
"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."
"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."
"It allows us to create logical data models. We can represent a database model in business terms, which is very useful for us."
"The data lineage feature is very valuable."
"The most valuable features are being able to visualize the data in the diagrams and transform those diagrams into physical database deployments. These features help, specifically, to integrate the data. When the source data is accumulated and modeled, the target model is in erwin and it helps resolve the data integration patterns that are required to map the data to accommodate a model."
"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."
"The most valuable feature of this solution is the reuse of common enterprise components and entities."
"The most valuable parts of this solution are the richness of its features and its easy interface."
"The solution is scalable. If a company needs to expand it, it's completely possible to do so."
"Its availability is very good."
"The most valuable feature is the completeness of HOPEX's meta-model. It's a strong meta-model that's rigid but comprehensive. It's a logical fit for our understanding of how we want things modeled in our database."
"An advantage is its accessibility."
"MEGA offers a more integrated GRC platform to facilitate enhanced coordination between the functions of Risk, Compliance, and Internal Audit on a single platform solution - HOPEX."
"The most valuable feature is that the software controls everything from a single management window."
"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."
"I would like the solution to be more user-friendly to deploy."
"This is a very complex product."
"The solution's reporting side needs to be improved."
"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."
"There is a lack of local support in the China region."
"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 modeling product itself is far and above anything else that I've seen on the market. There are certain inconsistencies when it comes to keeping up with other platforms' databases in the reverse-engineering process. It should also support more database platforms."
"It has a data domain where we load our data objects onto the tool but doesn't provide data governance capabilities such as cleansing or validating data."
"An area for improvement in MEGA HOPEX is its vast learning curve. The tool is also heavy, so that's a pain point. MEGA HOPEX is also tricky to use if you don't train for many hours."
"The interface must be improved."
"They do tend to push people to their professional services, instead of helping the customers with their problems. I understand this is their business. At the same time, however, they need to work on fact sheets or offer some program to help the customers who want to implement it themselves and to make it run properly in their environment."
"Lacking more out of the box integrations."
"This product is expensive and would be improved by lowering its price."
"It takes a long time to learn how to use HOPEX. It's hard to work with it because the user interface is bad. For example, if you want to build a complex system diagram, you need a lot of knowledge to do this correctly and make it readable. In MEGA, you need to create a report and it takes a long time to publish it. The publishing is offline. With RDoC, everything is online."
"The tool's UI should be more user-friendly."
erwin Data Modeler by Quest is ranked 3rd in Enterprise Architecture Management with 37 reviews while MEGA HOPEX is ranked 4th in Enterprise Architecture Management with 37 reviews. erwin Data Modeler by Quest is rated 8.6, while MEGA HOPEX 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 MEGA HOPEX writes "Interactive with good functionality and helps with productivity". erwin Data Modeler by Quest is most compared with SAP PowerDesigner, IDERA ER/Studio, Lucidchart, Visio and Avolution ABACUS, whereas MEGA HOPEX is most compared with Sparx Systems Enterprise Architect, LeanIX, ARIS BPA, Visio and Alfabet Enterprise Architecture Management. See our MEGA HOPEX vs. erwin Data Modeler 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.
