If you were talking to someone whose organization is considering IDERA ER Studio, what would you say?
How would you rate it and why? Any other tips or advice?
It is a good product but it needs improvement of the documentation process.
I would recommend IDERA ER/Studio, but people in my profession are divided by their loyalties. I am loyal to this product, but if you talk to another developer who has been using erwin all his life, that person might say, "Hey, erwin is better." I say ER/Studio is good but in the world of developers, people still have to evaluate things for themselves. I have no complaints. That's why I've been using it for so long. I rate it a nine out of ten. It's easy and fast to use.
Any advice would depend on the infrastructure, but just start using it more and more. It's mainly for developing databases. If you have a smaller number of tables and all of them are relational, you may not need this software. But, if you have a data warehouse that needs to be developed and you need to frequently implement changes to the databases, it will help. I rate the solution a rating of eight out of ten. I would consider it one of the best solutions on the market.
You will save time, switching from whatever product you're using. It's the best data modeling tool out there. It's fast. It can do what I need it to do. We connected to Oracle, MySQL, and SQL Server (as data sources) to this solution. I have plans to expand the use of the built-in tool functionality. However, I haven't had the time.
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.
ER/Studio is good. It is really user-friendly and you can start without much training. If modeling is a technique you know, you're familiar with all the concepts, you can sit with the tool and start doing the modeling. Not much training is needed.
There are a lot of options, so take the time to play with it a bit before you start doing things the hard way.
Especially with the Repository/Team Server installation, get Idera to install it for you. Just watch over their shoulder while they do it. Otherwise, just learn it and enjoy it. I rate this product at nine out of 10 because it does so much. It's so powerful. The only reason I don't give it a 10 is because it probably has things in it that I'll never use because I don't know how to use them.
Try to take advantage of as many of the features as you can. It has a wealth of time-savers and features that are extremely useful. We haven't been able to use all of them because we already had so much done. To try and use some of them by going back over thousands and thousands of tables and columns would have been impossible. If you are is just starting with it, if you can take advantage of the Data Lineage and some of the other interesting features that it has, it is definitely worthwhile. My rating comes from a purely selfish perspective, in the way I use it. For what I do, I give it an eight out of 10. The reason is - and this is partly our fault because we haven't finished, we haven't upgraded to newest release yet - that there are some buggy things in it that we still have to get resolved. For us, upgrading is very difficult because we have so many people, and we have to coordinate with our database people. Our services are now outsourced, so to coordinate things and get everybody on and get an upgrade done is not easy. Obviously, we try to avoid it as long as we can.
It's a good tool but we have not had much training, so we are really exploring it on our own. There are some features we are still working on with our stakeholders to implement. So my advice to other customers who are implementing this product is to really understand the full features of the product and try to implement all the features at the beginning. Get training in all areas of expertise before launching the product. I wish we could have done that from the beginning.
Which one is better and in which use cases?
Let the community know what you think. Share your opinions now!