IDERA ER/Studio Pros and Cons

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.

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.

We found a lot of duplication, a lot of non-conformity in the way our databases were designed. By identifying these situations, we're able to go back in and try to create a more standardized solution.

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.

It's much easier to develop the database structure and change it on the fly, rather than doing it manually in SQL Server itself. That saves time.

The most important features are logical and physical models that we can compare and develop. Also, the Data Dictionary can be created out of your studio. Finally, database schemas help understand the logic that's behind the scene, behind the SQL tables. Especially when there are a lot of them, the schemas help everyone understand the business processes.

Developing new dimensional models; for the data we're hosting, dimensional modeling is more useful.

The most valuable features are... those that enable me to represent the database to the development community and the business users.

We use the solution to create data models which describe our company's data architecture

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.

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.

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.

When validating the model, the ability to provide sub-models to developers, and generate a physical model from the logical, makes it easier to review a logical model with stakeholders.

The reverse engineering is the most important feature.

What I would like to see improved is the reliability of the releases, releases that are a little less buggy.

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.

We would always like to see Repository performance improve, checking in and checking out.

We did have a big issue when we upgraded to the 2016 version. The Team Server portion never did quite install correctly, and/or the database was corrupted, and we never figured it out.

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.

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.

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.

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.

It would be helpful if they could create a generic JSON database type, as a target database, rather than a specific one like Mongo.

The solution could be sped up, as it is a little slow (e.g., when it's doing its database compare).

The screens are a bit outdated. They could use a new look and feel.

The only thing I had an issue with was licensing, and the support was very good.

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 building the relationships there should be a little more flexibility.