ER/Studio has been my tool of choice for the last 15 years
June 21, 2017
ER/Studio has been my tool of choice for the last 15 years
Score 10 out of 10
Vetted Review
Verified User
Overall Satisfaction with ER/Studio
ER/Studio is used by my team and possibly by some other teams. I use it for logical and physical modeling of databases, both OLTP and data warehouses, as well as for applying incremental changes to the databases (deployments). I also use it to maintain consistent naming standards.
- ER/Studio is great for dividing logical and physical design. A logical model can be used with different physical platforms.
- Studio can a useful macro capability that allows me to apply the naming standards across the model with ease and consistency.
- ER/Studio does a very good job at comparing the model with the actual database and generating DDL scripts for production deployments.
- ER/Studio has an excellent reporting and model publishing capabilities allowing me to produce models in the HTML format and publish them for the team as needed.
- We recently moved to using AWS Redshift as our data warehousing platform. ER/Studio does not support Redshift.
- ER/Studio does not support conceptual data modeling.
- Increased quality of the data models.
- Increased productivity in data modeling and database development.
- Ability to share the models with the team.
- aqua, Toad Data Modeler and Visio
ER/Studio is the most mature, reach in features and quality and therefore useful. Unfortunately, it lacks compatibility with AWS Redshift.