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.
DBA at a consumer goods company with 201-500 employees
Real User
2018-08-09T06:47:00Z
Aug 9, 2018
Our primary use case is for building out data models. As the DBA, I am also responsible for modeling the OLTP databases as well as our warehouse. 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.
IT Specialist at a government with 10,001+ employees
Real User
2018-08-07T13:21:00Z
Aug 7, 2018
We're supposed to be using it for designing new data models, appending and editing data models. We're doing a lot of reverse engineering on our existing databases. But we have a plan in the works to begin using it as part of our data governance process, something we don't have currently.
Data Architect at a computer software company with 1,001-5,000 employees
Real User
2018-08-02T11:48:00Z
Aug 2, 2018
The primary use would be all the data modeling of the enterprise. People can access the data model through the portal: all the modeling and all the data dictionary, column-level documentation, glossaries, etc. We use the portal for maintaining those. The main tool that we use is IDERA Architect on the team portal.
IDERA ER/Studio is a powerful suite for business-driven data modeling that enables companies to create an enterprise architecture foundation for data governance. With round-trip support for multiple database platforms, data architects have the power to reverse-engineer, analyze, and optimize existing databases easily from diverse platforms. Data professionals can easily capture and share models, metadata, data sources, and glossaries across the organization for improved alignment between the...
Our primary use case of this solution is to design our database.
We use it for data modeling.
We use it to develop our data warehouse, it's the core server.
We use it for data modeling.
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.
We use it for data modeling.
Data modeling.
Our primary use case is for building out data models. As the DBA, I am also responsible for modeling the OLTP databases as well as our warehouse. 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.
We're supposed to be using it for designing new data models, appending and editing data models. We're doing a lot of reverse engineering on our existing databases. But we have a plan in the works to begin using it as part of our data governance process, something we don't have currently.
Data modeling and database design for PepsiCo.
The primary use would be all the data modeling of the enterprise. People can access the data model through the portal: all the modeling and all the data dictionary, column-level documentation, glossaries, etc. We use the portal for maintaining those. The main tool that we use is IDERA Architect on the team portal.