AWS Well-Architected Tool vs erwin Data Modeler by Quest comparison

"The product's most valuable feature is adaptability."

"The solution is excellent in providing a visual representation of a database and can generate DDL for implementing changes. We use DDL for logical purposes to review with business people, ensuring they have the required fields for processing. We also use it as a data dictionary for the physical data model to understand all the purposes of the terms. This helps us map the logical and physical terms with the business definition to understand our data."

"erwin has versioning so you can keep versions, over time, of those models and you can compare any version to any version. If you're looking at a specific database and you want to see what changed over time, that's really useful. You can go back to a different version or connect that to your change-control processes so you can see what was released when."

"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 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."

"It's a safeguard for me because I'm always concerned that somebody is free handing it and will forget a key coming from the parent. The migrating keys are a great feature. Identifying relationships, non-identifying relationships, and being visually right there to understand the differences are great features. erwin is key to being able to visually understand whatever the customer is requesting. They'll give you words on a paper, but once they can actually view it as a picture, it really comes to life. The data comes to life to where they understand exactly what they're asking for."

"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 allows us to reuse entities and attributes."

"One of the best aspects of the tool is its reverse engineering capability."

"They could provide a simplified process for building and deploying solutions in the cloud."

"I would like the solution to be more user-friendly to deploy."

"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."

"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."

"I would like the solution to be less rigid in terms of its theory."

"erwin is not as robust as a data warehousing project I've been on in the past."

"The solution's model mark could be better because it crashes sometimes."

"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."

"The erwin Data Modeler is quite complex to use."

"The platform’s pricing depends on the specific project requirements."

"There are no costs in addition to the standard licensing fees."

"It is not a very expensive solution. Only the licensing and maintenance fee needs to be paid."

"This company had bought the license for three years, and it's not an individual license. While you can buy a license for each individual, that would be very expensive. There is something called concurrent licenses where you can purchase licenses in bulk and 15 to 20 people can access the license and model. Concurrent licenses are scalable to the number of users and are proportional to the cost."

"Price-wise, erwin Data Modeler is okay. You can purchase a single license and it is not very expensive."

"Likewise, the solution is a little pricey."

"There are two license options and the pricing is reasonable."

"We've continued to use the product for many years and compared it with others on the market. The pricing is reasonable considering what the solution offers and what we pay. There are cheaper tools, but they may not be as robust and easy to use, so it's worth the money."

"The primary reasons that erwin was selected were that it was much more affordable for us [than Embarcadero] and it was easily maintainable."