IDERA ER/Studio Data Model Creation
Do you use this solution to create data models that describe your company’s data architecture? If so, please describe your use of the solution to accomplish this.
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.View full review »
The most valuable feature is data modeling, primarily, because it's something that has been lacking in our systems development for 20 years. There was no accountability for data structure.View full review »
Our databases can have well over 200 tables. Add in the views and we can hit 500 objects pretty quickly. We currently have over 30 databases. Without solid models, it would be impossible to manage all the interdependencies.
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.View full review »
We use it for data modeling. It is the way we communicate requirements, both the gathering and presenting of them. We also use it for putting together our metadata and publishing it.View full review »
We use the solution to create data models which describe our company's data architecture. It is a mix of design upfront when we get changes. We also use the data models after we've implemented changes.View full review »