IDERA ER/Studio Room for Improvement

What I would like to see improved is the reliability of the releases, releases that are a little less buggy. Also, 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. View full review »

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. For example, we are moving from 16 to 17. 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 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. I already mentioned this to my account manager. He said they will put me with one of the product development teams to have this kind of discussion. View full review »

They is a lot of room of improvement. I have emailed and have asked for things but nothing has been done. For example, 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. Another situation is that I need, and 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. 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. Those are the two main problems that I encounter today. View full review »

I've been an ERwin user for quite some time, almost 10 years. 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. We can directly relate to different keys but here it is a little more complicated than ERwin. View full review »

It would be helpful if they could create a generic JSON database type, as a target database, rather than a specific one like Mongo. Also, Business Objects doesn't seem to be very stable at the moment, so we've stopped using that. View full review »

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. View full review »

The number of options can be overwhelming at times. That is not necessarily a bad thing but for a newbie, it can be daunting. View full review »

When building the relationships there should be a little more flexibility. View full review »

This solution needs more precise documentation. View full review »