I have been working with data modeling tools. Personally, I have been working with Erwin for many years now. ER/Studio is something I am currently trying to evaluate for acquiring it for our organization. We are looking to adopt it for organizational use.

I am not actively working with the tools discussed. It was for my daughter. She needs to use it. I have been in IT for more than 30 years yet lack knowledge about new tools used for making websites and applications.

We use the solution for data modeling, including both relational and dimensional data models.

I used the solution mostly for forward engineering, designing new database structures, and reporting and analytics databases.

We use the solution to build data modeling activities. We also use it for reverse engineering with a cloud environment, like Snowflake, for example. We are starting to test integrating it with Collibra.

We maintain all of our enterprise models within ER Studio. This includes our data marts and our local systems. We have multiple people who use the web interface to look at the models.

I have experience working with various data architecture tools, and ER/Studio is one of them that I use in this capacity. We use it either to help an organization understand what data it has got or to design a database.

I am primarily using this solution for reverse engineering and database comparisons.

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.

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.

Data modeling.

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.

To develop an underlying platform upon which to base our data governance program by creating a central repository for maintaining and disseminating logical, physical models for our enterprise-wide databases.