Database Developer at a financial services firm with 1,001-5,000 employees
Real User
2018-11-28T08:48:00Z
Nov 28, 2018
The data modeling module is important to me because I am a database developer and designer... It's very fast, reliable, up-to-date, so easy to use, smooth.
DBA at a consumer goods company with 201-500 employees
Real User
2018-08-09T06:47:00Z
Aug 9, 2018
One of the valuable features is inheritance when joining tables. When setting up RI and domains and rules, ER/Studio does a lot of the grunt, boilerplate code that would otherwise have to be hand-coded.
IT Specialist at a government with 10,001+ employees
Real User
2018-08-07T13:21:00Z
Aug 7, 2018
We found a lot of duplication, a lot of non-conformity in the way our databases were designed. By identifying these situations, we're able to go back in and try to create a more standardized solution.
Database Designer at a manufacturing company with 1,001-5,000 employees
Real User
2018-08-05T06:48:00Z
Aug 5, 2018
We have a database design group of about 15 people. The Repository enables multiple people to work on the same model at the same time. We have fully integrated models, so we have one model for the enterprise data warehouse, one model for MDM, with a lot of sub-models in these things. People work on different parts of the model at different times. So the repository enables us to share the models, and keep track of what everybody is working on.
Enterprise Architecture Management (EAM) solutions are designed to help organizations effectively plan, design, and manage their enterprise architecture. These tools provide a comprehensive view of an organization's business processes, IT systems, and their relationships, enabling better decision-making and alignment between business and IT strategies.
Straightforward setup.
The data modeling module is important to me because I am a database developer and designer... It's very fast, reliable, up-to-date, so easy to use, smooth.
It's much easier to develop the database structure and change it on the fly, rather than doing it manually in SQL Server itself. That saves time.
We use the solution to create data models which describe our company's data architecture
The most valuable features are... those that enable me to represent the database to the development community and the business users.
Developing new dimensional models; for the data we're hosting, dimensional modeling is more useful.
The reverse engineering is the most important feature.
One of the valuable features is inheritance when joining tables. When setting up RI and domains and rules, ER/Studio does a lot of the grunt, boilerplate code that would otherwise have to be hand-coded.
We found a lot of duplication, a lot of non-conformity in the way our databases were designed. By identifying these situations, we're able to go back in and try to create a more standardized solution.
We have a database design group of about 15 people. The Repository enables multiple people to work on the same model at the same time. We have fully integrated models, so we have one model for the enterprise data warehouse, one model for MDM, with a lot of sub-models in these things. People work on different parts of the model at different times. So the repository enables us to share the models, and keep track of what everybody is working on.
It's easy to model and has a user-friendly interface.
I like the team portal because, once we upload, the entire team can see the model.