Relational modeling
Object definition tables for OLAP modeling
This version of relational modeling comes with a preview of the ability to use object definition tables to build a complete OLAP model with cubes, dimensions, hierarchies and other OLAP objects. This is a preview. Publishing of the model definition will follow with future releases.
Application selector
The application selector has been moved from the table tree to the Load queries and Scripts pages. This improvement was introduced to better reflect that tables are globally available while scripts and load queries belong to an application.
Export model/Export bundle
The Export Bundle option is renamed to Export Model and comes with a new dialog box where you can choose to include load queries, scripts, and the OLAP model.
Handling of missing tables
If you delete tables from the staging database, through means other than relational modeling, load queries for those tables are not deleted. In this case, the table is shown in relational modeling but is highlighted with a warning icon. You can then decide whether to re-create the table and its schema, or to delete all load queries and the table.
Staging table names
Starting with this version, you cannot create staging tables with names that conflict with integration tables. You cannot create staging tables that start with these prefixes:
- dEPM_
- WF_
- WFB_
- WFP_
- CO_
- Capex_
Existing tables that use these prefixes must be migrated to tables with different names.
If, prior to this release, a staging table has exactly the same name as an integration table, this table is hidden from the tables tree in Staging but is not deleted from the staging SQL Server database. The table's load queries are shown under the relevant Integration table.
You can create a new table with the schema and data of the hidden table by using a load query against the hidden table.