IDERA ER/Studio Reviews

We use it for data modeling. It is the way we communicate requirements, both for gathering and presenting them. We also use it for putting together our metadata and publishing it.

There are a lot of different ways we use the tool. One of the ways is that we do auditing of what's been billed to production to make sure it matches what we have designed. And it has also improved things in that we have design requirements for the DBA.

Because of all the various things we use it for, it has a high value within the organization.

The most valuable features are the various features for different databases, but mainly those that enable me to represent the database to the development community and the business users.

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.

We did not encounter stability issues in the past but lately, since they're undergoing the rewrite of their internal system, there is some stuff creeping in. We've had some stability issues in the last six months.

We haven't had any scalability issues.

Tech support hasn't been as good lately as it was in the past. It is down to "average."

Prior to using ER/Studio, there was ERwin in-house, but their tech support was horrible, their product was not very good. This was back in the early 2000s, so we switched over because ER/Studio was more flexible. It was able to reverse-engineer a database in under a minute, versus ERwin, which was taking over an hour. That performance was a big issue. Also, early on, and other than in the last six months, Idera's tech support was excellent.

I don't know enough about what the pricing is for other choices out there. I've only really worked on this one tool.

We looked at PowerDesigner, Oracle's native designer, and ERwin. We only did those three, four including ER/Studio. And this tool was, by far, at the time, the better one. Since that time, and now that we have more people in-house, ERwin, evidently, now has more features. I can't confirm or deny that, I don't know because I have never used ERwin. But, at the time, back in 2004, there was a big difference.

I really like ER/Studio personally, so for me, it's a nine out of 10. I like it because it doesn't let you make stupid mistakes - and it's easy to make a stupid mistake. The tool can save you a lot of trouble. The only other tool I used before this was Oracle Designer, back in the 90s. This is way better than that. I haven't used anything else, so I'm a loyal customer.

• Repository > Diagrams
• Security > Security Center
• Tools > Generate Reports
• Entity > Notes
• Attribute > Notes

• Diagram Versioning is not very intuitive
• Data Dictionary Bindings is not very intuitive

I've used it for three years.

No issues encountered.

Not with the current release.

It's good.

It's good.

I have personally used many modelling tools. My current company standardized on this one.

We used a vendor team who were good.

None the enterprise does not utilize all its capabilities thus, much of the work done is ported to other tools.

If using this tool to support a large team effort, get training for versioning

This application does a lot of things, as do competitor products, but the main reason to go with this product was the ability to create many automations, where we can improve our work and our process.

Organization, security, centralization.

The product is pricey.

About four years.

Sometimes our version is a little unstable. But I think this problem occurs because our version is old. We are in the migration process to the current version.

No.

Very good. When we need, they respond to us quickly.

I didn’t use other solutions in my work, only in tests.

A support member in my company helped with the initial installation.

The product can have a high price.

Yes. erwin and ePower.

Talk with other people before purchasing to learn about their experience with the product.