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

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

"There is absolutely no problem with the stability."

"The solution's ability to compare and synchronize data sources with data models is fantastic. We use it for that on a regular basis to make sure that changes haven't been made to the database outside of the modeling process. I can take existing databases and reverse engineer them and understand their structure within 15 minutes. If I didn't have Data Modeler it would take hours. It increases our productivity and helps in understanding our legacy application."

"Quest can create conceptual and physical data models to facilitate effective communication between business and IT. It can also integrate expertise from various engineering and database systems within your organization to enhance data management and administration."

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

"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 principal feature that I liked is that the solution has a very graphic interface."

"The data lineage feature is very valuable."

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

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

"The reverse engineering in Oracle Databases needs improvement, as there are issues."

"I still use Visio for conceptual modeling, and that's mainly because it is easier to change things, and you can relax some of the rules. DM's eventual target is a database, which means you actually have to dot all the Is and cross all the Ts, but in a conceptual model, you don't often know what you're working with. So, that's probably a constraint with erwin. They have made it a lot easier, and they've done a lot, but there is probably still room for improvement in terms of the ease of presentation back to the business. I'm comparing it with something like Visio where you can change colors on a box, change the text color and that sort of stuff, and change the lines. Such things are a whole lot easier in Visio, but once you get a theme organized in erwin, you can apply that theme to all of the objects. So, it becomes easier, but you do have to set up that theme."

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

"It is not a very stable solution. I rate the stability five out of ten."

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

"We are planning to move, in 2021, into their server version, where multiple data modelers can work at the same time and share their models. It has become a pain point to merge the models from individual desktops and get them into a single data model, when multiple data modelers are working on a particular project. It becomes a nightmare for the senior data modeler to bring them together, especially when it comes to recreating them when you want to merge them."

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

"I would like to see improved reporting and, potentially, dashboards built on top of that. Right now, it's a little manual. More automated reporting and dashboard views would help because currently you have to push things out to a spreadsheet, or to HTML, and there aren't many other options that I know of. I would like to be able to produce graphs and additional things right in the tool, instead of having to export the data somewhere else."

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

"erwin is expensive compared to other solutions. We are paying almost $6,000 per seat a month."

"Pricing is very high compared to any other product."

"There is either a one-year or three-year license. It is not a pay-as-you-go license like a SaaS solution. It’s more of a traditional licensing. They are a little bit on the pricier side."

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

"Though the solution is not cheap, it's worth the money."

"The pricing of the solution is cheap. I rate the pricing a five out of ten."

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

"The solution is expensive."