Many organizations are now creating views that pull data from multiple databases instead of replicating data into new tables.
ER/Studio 21.0 extends support for this approach, enabling teams to model views that reference objects across databases. This is especially relevant in data warehousing environments, where reducing storage duplication and improving agility are key priorities.
In this on-demand session, see how ER/Studio supports external views across platforms including SQL Server, Synapse, and Snowflake.
Through a practical demonstration, you’ll learn how to model cross-database dependencies, work with replica objects, and maintain traceability across systems.
In modern data warehouse architectures, data is often organized across multiple layers, with views pulling data from different databases rather than storing multiple copies.
This session shows how ER/Studio helps you:
ER/Studio supports modeling of external views by reverse engineering dependencies, creating replica objects for referenced tables, and enabling connections back to source systems using Compare & Merge. This approach helps teams better understand how data is structured and connected across multiple databases.
Have questions or want to see it in your environment? Schedule a demo with our team.
External views are views that pull data from tables in other databases. ER/Studio supports modeling these views and their dependencies.
ER/Studio creates replica objects that capture basic metadata about tables referenced from other databases, allowing those tables to be used in modeling and view creation.
Using Compare & Merge, replica objects can be linked to the actual tables in their source databases, enabling navigation and traceability.
External views allow teams to reduce data duplication across layers while maintaining flexibility and visibility into how data is used across systems.
