TrustRadius Insights for ER/Studio Data Architect are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.
Business Problems Solved
ER/Studio is highly regarded for its ability to simplify the process of designing logical and physical ER data models compared to other tools on the market. Users have found that the integrated tool 'Team server' allows for easy access to the storage repository of models for a wider audience, including both technical and business teams. With ER/Studio, generating DDLs to create a physical layer has become much more efficient, minimizing data engineering work. Additionally, exporting models is a breeze, enabling users to effortlessly generate schema reports and database creation scripts.
Another notable use case of ER/Studio is in the design of supply chain ETL data models and mapping, which has proven instrumental in avoiding potential performance issues. Moreover, creating various diagrams like business process models, context diagrams, and data flow diagrams has been made easier with ER/Studio, aiding in the identification of flows that can be automated. The tool's interface also facilitates the design of logical models after discussions with the business, providing a pictorial view of different schemas that is easy to understand.
ER/Studio goes beyond data modeling and supports important aspects such as data lineage and data governance. It helps capture and record true business requirements while transforming them into a cohesive database design. For data modeling teams working on application databases and data warehouse designs, ER/Studio simplifies the process by providing consistent naming standards and an intuitive user experience. The tool's capabilities extend to managing physical model naming standards and all data models within an organization.
Importing ETL mappings and managing data lineage are powerful features that users find particularly valuable. Whether it's logical modeling or physical modeling for OLTP or data warehouses, ER/Studio enables users to make incremental changes seamlessly. Its ability to maintain consistent naming standards further solidifies its reputation as one of the best data modeling tools available.
In terms of usability, ER/Studio stands out as user-friendly, easy to learn, and efficient. It caters to both small departments and large organizations, providing a consistent methodology for database standards and needs. Furthermore, IT teams can generate data model images, facilitating communication and collaboration across different teams within an organization. With its robust features and user-friendly interface, ER/Studio has become the go-to solution for many businesses looking to manage their data models effectively.
Loading Reviews List....
ER/Studio Data Architect Reviews
1 Review
InformationComputer Software1
Search is temporarily unavailable. Filters are still applied.
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.
Pros
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.
Cons
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.
Likelihood to Recommend
ER/Studio is great for both logical and physical layers of database modeling. It does not support conceptual data modeling though. It should be used in both transactional and warehouse modeling. It is useful for enforcing database naming conventions, good design practices and comprehensive reporting on database models, including publishing the models for the wider team.