We performed a comparison between erwin Data Modeler by Quest and IDERA ER/Studio 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.
"It is a scalable solution...The technical support team is fine."
"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 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."
"The generation of DDL saved us having to write the steps by hand. You still had to go in and make some minor modifications to make it deployable to the database system. However, for the data lineage, it is very valuable for tracing our use of data, especially personal confidential data through different systems."
"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."
"It has centralized storage so that a data model can be shared by different teams."
"There is absolutely no problem with the stability."
"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."
"One of the valuable features is inheritance when joining tables. When setting up RI and domains and rules, ER/Studio does a lot of the grunt, boilerplate code that would otherwise have to be hand-coded."
"We have a database design group of about 15 people. The Repository enables multiple people to work on the same model at the same time. We have fully integrated models, so we have one model for the enterprise data warehouse, one model for MDM, with a lot of sub-models in these things. People work on different parts of the model at different times. So the repository enables us to share the models, and keep track of what everybody is working on."
"The tool is simple to use."
"The data modeling module is important to me because I am a database developer and designer... It's very fast, reliable, up-to-date, so easy to use, smooth."
"Modeling with Data Architect: We can quickly reverse-engineer a database from an existing database or create a model from scratch."
"Data lineage tracking: It allows us to identify upstream and downstream systems using data."
"Developing new dimensional models; for the data we're hosting, dimensional modeling is more useful."
"We have been able to quickly create models for our enterprise-wide databases, even when some of them are third-party databases."
"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."
"This is a very complex product."
"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 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."
"The solution's model mark could be better because it crashes sometimes."
"The erwin Data Modeler is quite complex to use."
"The interface must be improved."
"I would like the solution to be less rigid in terms of its theory."
"It would be helpful if they could create a generic JSON database type, as a target database, rather than a specific one like Mongo."
"What I would like to see improved is the reliability of the releases, releases that are a little less buggy."
"Tech support is a sticking point with me. I am really disappointed in the tech support. We pay for the Platinum level. It takes hours to get a response."
"They allow functionalities to be released before the full tests for catching and correcting errors are completed."
"The visual presentation is a little too colorful and seems that it is dumbed down."
"We would always like to see Repository performance improve, checking in and checking out."
"The only thing I had an issue with was licensing, and the support was very good."
"I'd like the ability to debug the errors ourselves instead of having to call them. There are certain types of errors that, I wouldn't say they come up regularly, but when you have an error it is very often the same type of error. Knowing that it's a Type III or Type I, it would be nice to have some kind of debugging facility for us to use to find out where the problem that threw that error occurs. That would be a really cool feature."
erwin Data Modeler by Quest is ranked 3rd in Enterprise Architecture Management with 37 reviews while IDERA ER/Studio is ranked 10th in Enterprise Architecture Management with 34 reviews. erwin Data Modeler by Quest is rated 8.6, while IDERA ER/Studio is rated 8.4. 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 IDERA ER/Studio writes "The solution has important reverse engineering features, but it needs a single sign-on feature". erwin Data Modeler by Quest is most compared with SAP PowerDesigner, Visio, Lucidchart, Sparx Systems Enterprise Architect and AWS Well-Architected Tool, whereas IDERA ER/Studio is most compared with SAP PowerDesigner, Sparx Systems Enterprise Architect, Toad Data Modeler, erwin Evolve by Quest and LeanIX. See our IDERA ER/Studio 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.
