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.
"We can create mappings in erwin and possibly data dictionaries."
"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 lets us import different types of models from various databases."
"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."
"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."
"It has centralized storage so that a data model can be shared by different teams."
"It supports a wide variety of databases, including the latest ones. We have chosen to go for a cloud-based database, and it supports that, which is very useful."
"The fitting model is very intuitive."
"IDERA keeps up with the versions of Oracle and SQL Server that I'm using. I mostly use SQL Server and when there are new features, a new type of index, for example, IDERA also includes them in upgrades of the data modeling tool."
"The tool is simple to use."
"It's easy to model and has a user-friendly interface. I like the team portal because, once we upload, the entire team can see the model."
"Modeling with Data Architect: We can quickly reverse-engineer a database from an existing database or create a model from scratch."
"Straightforward setup."
"We can track changes to our data models and tie those changes back to specific tasks or efforts that we identify."
"The data modeling and reverse engineering features are most important to us."
"Valuable features include the ability to visually represent what the database tables are going to look like and their relationships. Also, the ability to document the definitions of the tables and the columns that are in a table so that we can communicate what the data is and how it should be used."
"I am not so happy with its speed. Sometimes, it can have problems with connections."
"I'd really like to see the PDF function become available. It would make my life much easier than what it is at the moment because whenever I need to collaborate with people that do not have erwin, I have to go through the wonkiness of going to Word and then save it from Word into PDF. There's a lot of differences between erwin 4.4 and 2020."
"I would like the solution to be more user-friendly to deploy."
"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."
"It does not have a cloud application."
"There is a lack of local support in the China region."
"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 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."
"We would always like to see Repository performance improve, checking in and checking out."
"The solution could be sped up, as it is a little slow (e.g., when it's doing its database compare)."
"Whenever there is a new version, there are a lot of release notes on the technical side of it, but I would like to be told why are we doing the upgrade... What I would like to really see is how this benefits us from the business point of view. What are the real benefits that the user gets? I want some kind of way white paper. The release notes describe the technical enhancements but, from the layman's point of view, if someone asks me what are the business benefits of this upgrade, I don't have any documentation to explain it to the business."
"The only thing I had an issue with was licensing, and the support was very good."
"I would like to upload, a database with about 3,000 tables. It takes so much time and, finally, it freezes the whole solution so that I actually cannot work with that environment. For the data warehouse, it's fine because I have 20 or 30 tables. It works fine. But, when I reverse-engineer the database with 3,000 tables, it freezes and it's hard to upload and reverse-engineer such environments in ER/Studio."
"One limitation I have found in ER/Studio is that when you want to make some changes to the table definitions, you have to go item by item. You cannot do it globally. Another issue concerns defining the foreign keys between the different tables. It is a little more tedious in the ER/Studio than in ERrwin. With ERwin it is direct."
"The number of options can be overwhelming at times. That is not necessarily a bad thing but for a newbie, it can be daunting."
"when there are some links to the external databases, if this database is not structured it is not uploaded. It gives me errors and I cannot see the view that was created on this structure and I cannot change those views, even manually. It skips the views. I have to ignore those views. I cannot re-upload them because it gives me an error."
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 33 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.
