TrustRadius Insights
ER/Studio is highly regarded for its ability to simplify the process of designing logical and physical ER data models compared to other …
Starting at $1,470.40 one-time fee per user
View PricingOverview
What is ER/Studio Data Architect?
ER/Studio is a database development and management tool from Embarcadero Technologies (acquired by Idera) in California.
Recent Reviews
Pricing
Entry-level set up fee?
- No setup fee
For the latest information on pricing, visithttps://store.idera.com/buynow/onlinest…
Offerings
- Free Trial
- Free/Freemium Version
- Premium Consulting/Integration Services
Starting price (does not include set up fee)
- $1,470.40 one-time fee per user
Product Demos
Governing data with ER/Studio Data Architect
YouTube
Product Details
- About
- Integrations
- Competitors
- Tech Details
- Downloadables
- FAQs
What is ER/Studio Data Architect?
ER/Studio Data Architect is a data architecture and database design software. It is compatible with multiple database platforms. The tool is used to create and manage database designs, as well as to document and reuse data assets. It aims to enable companies to create and maintain entity relationship diagrams with detailed metadata.
ER/Studio Data Architect offers several benefits, including:
Round-trip database support: Data architects can reverse-engineer, analyze, and optimize existing databases from diverse platforms. Such platforms include relational and NoSQL data sources.
Collaborate and share: Multiple users can collaborate and share data assets across modeling projects in the model repository.
Design a business-driven enterprise data architecture: ER/Studio Data Architect enables companies to design a data architecture that is aligned with their business needs.
Enforce organizational standards: The tool enforces organizational standards in data modeling throughout the organization.
Manage hierarchical models such as JSON, MongoDB, Google BigQuery in the same way and graphical user interface as relational models.
ER/Studio Data Architect is designed for a variety of professionals who are involved in data modeling, database design, and data management. These professionals include:
Data architects can use ER/Studio Data Architect to create and maintain entity relationship diagrams, as well as to document and reuse data assets.
Database administrators can use the tool to reverse-engineer, analyze, and optimize existing databases, ensuring optimal performance and compliance with organizational standards.
Data analysts can use ER/Studio Data Architect to understand and analyze data structures, relationships, and metadata across different data sources.
Data modelers can leverage the tool to design and maintain logical and physical data models for various database platforms.
Developers can use ER/Studio Data Architect to generate and change database schema scripts, ensuring consistency between the data model and the actual database.
Business analysts can use the tool to understand and document business requirements and data needs, facilitating better collaboration between business and information technology teams.
The top use cases of ER/Studio Data Architect are:
Analyze and design platform-independent logical data architecture.
Design and construct platform-specific physical databases.
Build and maintain large, complex database applications.
Consolidate, report, and re-use metadata across the enterprise.
Describe information requirements and technical design of data assets.
Understand and design data assets in a universal way without having to understand code.
Control how changes in requirements are implemented.
Allow data architects to support a data governance program.
The top strengths of ER/Studio Data Architect are:
Broad range of database platform support.
Enterprise-level capabilities.
Visual data lineage and flow modeling.
Full dimensional modeling for data warehousing and business intelligence.
Business data objects to bridge the gap between developers and data architects.
Agile change management, nested submodels, and universal mappings.
Superior compare and merge.
Built-in business glossary.
Rich macros supported by full programming language.
ER/Studio Data Architect Features
- Supported: Builds out an enterprise data model as entity relationship diagrams (ERD)
- Supported: Creates a data catalog to support data governance initiatives, and metadata management
- Supported: Discovers and documents existing data assets
- Supported: Lays the foundation for robust data governance and data management
ER/Studio Data Architect Screenshots
ER/Studio Data Architect Video
ER/Studio Data Architect Integrations
- Collibra Data Intelligence Cloud
- WhereScape 3D
- Bluemetrix Data Manager
- Silwood Safyr
ER/Studio Data Architect Competitors
ER/Studio Data Architect Technical Details
| Deployment Types | On-premise |
|---|---|
| Operating Systems | Windows |
| Mobile Application | No |
| Supported Languages | English |
ER/Studio Data Architect Downloadables
Frequently Asked Questions
ER/Studio is a database development and management tool from Embarcadero Technologies (acquired by Idera) in California.
ER/Studio Data Architect starts at $1470.4.
erwin Data Modeler, IBM InfoSphere Data Architect, and SqlDBM are common alternatives for ER/Studio Data Architect.
The most common users of ER/Studio Data Architect are from Mid-sized Companies (51-1,000 employees).
Comparisons
Compare with
Reviews and Ratings
(11)
Community Insights
TrustRadius Insights are summaries of user sentiment data from TrustRadius reviews and, when necessary, 3rd-party data sources. Have feedback on this content? Let us know!
- Business Problems Solved
- Recommendations
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.
Users have made several recommendations for the software based on their experiences and needs. The most common recommendations are as follows:
Consider the importance of metadata: Users advise considering the significance of metadata in data modeling tools. They suggest paying for a quality tool to ensure higher quality database designs.
Get proper training: Users highlight the importance of receiving proper training to effectively use the software. This recommendation emphasizes that training can enhance users' understanding of its features and functionalities, enabling them to maximize its potential.
Verify compatibility with specific databases: While users appreciate that the software supports a variety of databases and is platform independent, they suggest checking compatibility with specific databases before use. This recommendation encourages users to ensure that their preferred databases are compatible with the software to avoid any potential issues or limitations during their data modeling process.
These recommendations provide valuable insights into the software's strengths, such as its versatility and ease of use, while also highlighting areas where improvements could be made, such as the addition of an API and automated features like data lineage and database entity import.
Attribute Ratings
Reviews
(1-1 of 1)Companies can't remove reviews or game the system. Here's why
October 07, 2015
ER\Studio: The Model Modeling tool
We use ER/Studio within our data modeling team here at UConn Health. I'm the lead data modeler and I'm responsible for the maintenance and administration of the ER\Studio application and repository. We use it for our application databases (3NF) and data warehouse database (Dimensional) designs. I've found it to be a very useful tool and makes creating the physical database as easy as a few clicks of a button. Of course there is effort in doing the analysis and creating the conceptual and logical models but writing DDL is a thing of the past with ER\Studio.
- ER\Studio supports the concept of a domain. You can create a custom domain (data type) and give it a name and use it as the data type for attributes. I use this to define my surrogate PK and several other "standard" attributes we populate into every relation (table).
- ER\Studio supports the coding of Macros. This is VB code that leverages their API to automate manual process. Very helpful as you could imagine. They supply a large set of pre-canned macros and are very good about helping you write your own if you need help. I have several macros that help me implement naming conventions on attributes and FK names.
- The repository is a handy feature that allows you to save off your models to a database to be safe and also to allow for collaboration between other modelers on you team.
- Several different licensing models allow for flexibility, usage. They support a single user workstation as well as concurrent licensing, for multiple part time users.
- ER\Studio licensing can be cumbersome and upgrading from one version to another usually takes several phone calls and emails to the licensing group to get the update installed and running.
- The repository can be slow when the model count gets larger. By large I mean 20 to 30 models.
- A nice feature that I would like to see is table comments be displayed on the model along with the attributes. Currently you have to choose between the two.
- Using ER\Studio to create models and eventually the actual database schema allows for a picture that is understandable to the customer and saves significant time writing DDL to create the database objects (tables, indexes, relationships, constraints...)
- A nice customer interface tool so you can create a web based interface to the metadata for a particular design.
- The tool also supports sub-models so you can break a large project into smaller parts, I find this feature very helpful.
- Sybase Power Designer Data Architect and CA ERwin
My first modeling tool was Sybase's Power Designer and it was a fine tool to get the job done. When I changed companies 10 years ago I was introduced to ER\Studio and have been using that ever since. More recently I looked into CA ERwin and found it to be unintuitive but to be fair I didn't spend a lot of time trying to figure it out.
No
We have the basic support; not even sure premium support is available. We get good responses from their support staff and they are very helpful with righting macros for you.
No
When I first starting working with macros and I had a question, the support person didn't just help me she actually wrote the macro for me and I've used it as a template for several other macros.