When you manage multiple DataWorks workspaces, applying a consistent data warehouse plan across all of them requires centralized model governance. The Modeling Workspace feature lets you designate one workspace as the Model Design Workspace, from which you perform unified data warehouse planning, Dimensional Modeling, and metric definition for all associated workspaces. This topic describes when to use the Modeling Workspace and how to configure it.
When to use the Modeling Workspace
The Modeling Workspace is designed for teams that manage multiple DataWorks workspaces and need a single control point for data model governance. Consider this setup if your team experiences any of the following:
-
Different teams are developing models independently across separate workspaces, making it hard to enforce consistent standards.
-
Changes to a shared model must propagate to multiple downstream workspaces, but there is no centralized control point.
-
You want to separate model design from ETL (Extract, Transform, Load) data development.
If your team works within a single workspace, this feature is not necessary.
Key concepts
DataWorks Intelligent Data Modeling introduces two workspace roles:
-
Workspace for Data Model Design: The central hub for model designers. All models for associated Data Development Workspaces are created and managed here. All model changes must originate here.
-
Workspace for Data Development: Used by data engineers for Model Publishing and ETL data development based on published model designs. The detailed model design is not visible or directly editable in this workspace.
After a model designer establishes the relationship between a Workspace for Data Model Design and its associated Data Development Workspaces, they can publish models — including Aggregate Table, Dimension Table, and Fact Table — and choose to materialize each model into any of the associated Data Development Workspaces.
Example: A model designer creates Model 1 in the design workspace Project_1. After this model is materialized and deployed to Data Development Workspaces Project_2 and Project_3, any subsequent modifications to Model 1 must be made in Project_1. The design is not visible or directly editable in Project_2 or Project_3.
A Workspace for Data Model Design can also act as a Data Development Workspace — you can choose to materialize models into it. However, once Project_2 and Project_3 are configured as Data Development Workspaces, they cannot be designated as a Model Design Workspace.
Prerequisites
Before you begin, make sure you have:
-
Workspace Administrator permissions for every workspace you want to add or remove as a Data Development Workspace
-
Confirmed that the target workspace has not already been added as a Workspace for Data Development
Configure workspace mappings
Follow these steps to configure the mapping between a Model Design Workspace and its Data Development Workspaces. After this mapping is set, you can select a target workspace during Model Publishing.
-
Go to the Data Layer page.
-
Log on to the DataWorks console. In the top navigation bar, select the desired region. In the left-side navigation pane, choose Data Development and O\&M \> Data Modeling. Select the desired workspace from the drop-down list and click Go to Data Modeling.
-
In the top navigation bar of the Data Modeling page, click Data Warehouse Planning. The Data Layer page appears.
-
-
On the Data Warehouse Planning page, click Workspace for Data Modeling in the left-side navigation pane.
-
In the Data Model Workspace Configuration section, click Modify Configuration. This section shows the current Workspace for Data Model Design and its associated Data Development Workspaces.
On the Modify Configuration page, you can add or remove only workspaces for which you have Workspace Administrator permissions.
-
To add a workspace: click the Workspace for Data Development drop-down list, select the target workspaces, click OK, and then click Submit. The selected workspaces are added as Data Development Workspaces.
-
To remove a workspace: click Delete next to the workspace you want to remove, and then click Submit. The mapping between the current Modeling Workspace and the selected Data Development Workspace is removed.
-
-
After saving the configuration, the Change Records section on the Modeling Workspace page shows all configuration changes made by Workspace Administrators.
Limitations
| Scenario | Limitation |
|---|---|
| Adding a workspace mapping | Only workspaces where your account has Workspace Administrator permissions can be selected. A workspace already added as a Workspace for Data Development cannot be selected again. |
| Removing a workspace mapping | Only mappings for workspaces where your account has Workspace Administrator permissions can be deleted. |
What's next
After configuring the workspace mapping and designing a model, select a target Data Development Workspace when you publish the model. For more information, see Model Publishing.