We performed a comparison between erwin Data Modeler by Quest and No Magic MagicDraw based on real PeerSpot user reviews.
Find out in this report how the two Business Process Design solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The product lets us import different types of models from various databases."
"We find that its ability to generate database code from a model for a wide array of data sources cuts development time. The ability to create one model in your design phase and then have it generate DDL code for Oracle or Teradata, or whichever environment you need is really nice. It's not only nice but it also saves man-hours of time. You would have to take your design and just type in manually. It has to take days off out of the work."
"We can create mappings in erwin and possibly data dictionaries."
"The solution is good for organizing the data and the scripting part is very powerful. It's easy to create technical scripts for models."
"Being able to point it to a database and then pull the metadata is a valuable feature. Another valuable feature is being able to rearrange the model so that we can display it to users. We are able to divide the information into subject areas, and we can divide the data landscape into smaller chunks, which makes it easier to understand. If you had 14 subject areas, 1,000 entities, and 6,000 columns, you can't quite understand it all at once. So, being able to have the same underlying model but only display portions of it at a time is extremely useful."
"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."
"I have worked with erwin Data Modeler for quite some time and familiarity is its most valuable feature."
"We use the Forward and Reverse Engineering tools to help us speed things up and create things that would have to be done otherwise by hand. E.g., getting a database into a data model format or vice versa."
"The most valuable feature is the amount of flexibility that one has to model, which is great for an individual."
"The technical support is very good."
"I would rate MagicDraw a nine out of ten because of the price. Enterprise Architect has a lot of bugs and MagicDraw is a lot more accurate and flexible. It's a level better."
"It is pretty easy to use. It is pretty versatile."
"The most valuable feature of No Magic MagicDraw is the simulation capabilities and interface."
"It is very user-friendly, and the customer service is really good."
"The most valuable feature is the ability to quickly build multiple layers within the organizational and business process environments, as well as in the SysML product environments, and converting to files that can be accessed by clients who do not have a system and a teamwork server access."
"I think one of the key things is the plugins for integration with requirements management tools like Doors"
"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."
"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 interface must be improved."
"I am not so happy with its speed. Sometimes, it can have problems with connections."
"Although Quest Software has made tremendous strides in recent years, they need to evolve more in the big data arena; erwin Data Modeler could use a little more work when it comes to big database designs."
"I love the product. I love the ability to get into the code, make it automated, and make it do what I want. I would like to see them put some kind of governance over the ability to make changes to the mart tables with the API, so that instead of just using the modeler's rights to a table -- it has a separate set of rights for API access. That would give us the ability to put governance around API applications. Right now a person with erwin and Excel/VBA has the ability to make changes to models with the API if they also have rights to make changes to the model from erwin. It's a risk."
"Complete Compare is set up only to compare properties that are of interest to us, but some of the differences cannot be brought over from one version of the model to another. This is despite the fact that we are clicking to bring objects from one place to another. Therefore, it's hard to tell at times if Complete Compare is working as intended without having to manually go into the details and check everything. If it could be redesigned to a degree where it is easier to use when we bring things over from one site to another and be sure that it's been done correctly, that would be nice to have. We would probably use the tool more often if the Complete Compare were easier to use."
"erwin is not as robust as a data warehousing project I've been on in the past."
"There's lots of documentation. They process multiples of guides. They've got all kinds of guides and documentation out there, but it's kind of hard to find. There are a lot of videos. You can go to YouTube and find videos on how it's been used in different ways, but it just kind of scratches the surface."
"It's very focused on specific modern languages and it doesn't do necessarily general systems software engineering with diagrams. They should expand the diagram types for the languages."
"It would be better if the User Interface were updated. At the moment, it's a classic environment. It reminds me of the old Windows interface, for example, Windows 95. It would be better to make it more user-friendly. It would also be better if it could integrate with SAP solutions. It isn't easy to find experts in the field. It's hard to find people around the globe that have the necessary skills and expertise to manage this solution. For example, in our case, we needed someone with refrigeration knowledge that also knew how to use the tool, and that was a challenge. We also had issues relating to erasing. Sometimes, it kept it in the background and didn't erase it at all. We had to review the entire list to ensure that the item was deleted."
"The licenses are expensive compared to similar tools. At the moment, the user is open to using MagicDraw if it's 15% more than other solutions. If it were to cost any more, they wouldn't use it."
"The cost of upgrading the product should be lower."
"The UI UX of the tool is not really user-friendly and needs to be completely reformed."
"There are some technical features that you have to study and do research on to be able to understand."
"The price of the solution could be reduced."
erwin Data Modeler by Quest is ranked 9th in Business Process Design with 37 reviews while No Magic MagicDraw is ranked 10th in Business Process Design with 17 reviews. erwin Data Modeler by Quest is rated 8.6, while No Magic MagicDraw is rated 8.2. 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 No Magic MagicDraw writes "Pretty easy to use and versatile, but doesn't support code engineering and can be overly complicated at times". erwin Data Modeler by Quest is most compared with SAP PowerDesigner, IDERA ER/Studio, Visio, Lucidchart and MEGA HOPEX, whereas No Magic MagicDraw is most compared with Sparx Systems Enterprise Architect, Visio, Visual Paradigm, Lucidchart and IBM System Architect. See our No Magic MagicDraw vs. erwin Data Modeler by Quest report.
See our list of best Business Process Design vendors.
We monitor all Business Process Design 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.
