ER/Studio Data Architect

The Best Data Modeling Tool In The Industry:

Learn More

The best way to learn more about how ER/Studio can help you and your organization is to download a free, fully functional, 14-day trial. You do not need to provide any credit card information.

Not all data modeling tools are created equal.  Advanced capabilities differentiate suitable data models from excellent data models.    

Do you need a tool that can do more than just create logical and physical data models, propagate changes from one model to the other in both directions, create database scripts, and reverse-engineer databases?

Then, you need ER/Studio Data Architect.

Key Features



Data Modeling Tool with Thick Client Plus Web Portal

In addition to its thick desktop client, ER/Studio has a unique, IDERA-built web portal for collaboration on data models, metadata, and glossaries.

You can also schedule a personalized product demonstration with an IDERA industry expert.



Multiple Physical Data Models

ER/Studio allows multiple physical data models in the same model file. The physical data models can be radically different from the logical data model.

ER/Studio includes business data objects that are the building blocks of conceptual data models.

Conceptual Data Model With Business Data Objects



Logical And Physical Data Segregation 

ER/Studio maintains the separation of logical and physical data models. This reduces the number of models needed and the complexity of the tasks required to maintain best practice during the change process.


Roll-Up And Roll-Down Multiple Relationships

ER/Studio can roll-up and roll-down multiple relationships in physical data models when collapsing levels in supertype-subtype hierarchies.

ER/Studio can include views in the logical data model, which users can then generate into the physical data models. Alternatively, you can mark views in the logical data model as logical-only (perhaps for reporting or integration requirements).

Logical Data Models Views



Break DDL Scripts Into Smaller Files

ER/Studio can break data definition language scripts into smaller, more manageable files when creating the databases.


Manage Three Or More Data Models In A Single File

ER/Studio can manage three or more data models for database migrations in a single model file. This makes it easier to track similarities and differences, as well as the data mappings that are necessary for a successful database migration.


Import ETL Code With Metadata

ER/Studio can use the built-in import bridge for metadata to import extract-transform-load code for database migrations. It will create several physical data models representing the source and target databases in a single file, linking them together using visual data lineage.

ER/Studio Data Architect includes the ability to view and relate business terms to data modeling assets. ER/Studio Team Server can then graphically display these relationships and push the industry standard data governance tools, enabling data architects to contribute knowledge to the data governance project.

Contribute To Data Governance



Model NoSQL

ER/Studio allows NoSQL models such as MongoDB to be modeled as a standard physical data model. Users can apply the standard design and documentation practice of linking logical and physical data models in the standard tool.


Roll-Down Table Into Multiple Child Tables

ER/Studio can roll-down a table into several child tables in a single operation.


Link Transformations Back To Logical Data Models

ER/Studio remembers the transformations that you carry out while denormalizing physical data models. It links the transformations back to the objects of the logical data model and can display the state of the model before and after the transformation.

ER/Studio can record data lineage for database migrations in both logical and physical data models. This allows users to model high-level designs for data movements.

Logical And Physical Data Models Data Lineage



View Data Lineage Graphically

ER/Studio can graphically represent information concerning the data lineage for database migrations in the user interface.

ER/Studio does not apply roll-ups or roll-downs for supertype-subtype hierarchies to every entity at that level of the hierarchy. This is important when models have a lot of subtyping and provides control to the user


Roll-Up And Roll-Down Not For Every Entity