Modules

Modules combines fact and dimension data into structured and consistent data sets. Dimensions can be scanned and/or reduced in reference to the fact tables. Fact tables can be partitioned, aggregated or used in star models against dimensions. SSAS modules has additional settings to use the data warehouse data sets to produce multidimensional and tabular databases for use in analysis and reporting.

Profitbase Studio supports following types of modules:

SSAS Database / OLAP modules

This type generates a set of tables/views in the data warehouse database.
In addition the SSAS databases are created, or updated, and processed.

Following modes are supported:

  • Multidimensional (MOLAP)
  • Tabular 
Data Warehouse Output modules

This type generates a set of tables/views in the data warehouse database. These data can then be consumed by other systems. 

Following modes are supported:

  • Generic module with configurable fact table handling (aggregation, table, *-model).
  • Profitbase WebPlan and Sim7 modules with fixed month aggregation.

The structure in a Profitbase Studio module is based on SSAS Database structure. It includes the following elements:

Studio SSAS  Description/content

Module Group

Database

This is the container that contains shared dimensions (dimensions linked to/used by module definitions).

For SSAS databases, it also contains definitions for the target SSAS database and of the connection that the SSAS service use to connect to the data warehouse database.

Module Sub Group

Multidim:
Cube

Tabular: Model

This is the sub container for organizing different groups of module definitios.

For SSAS, this relates to Cubes and contains Actions and Business Logic items (sets, scripts etc.). 

For Tabular SSAS modules there can only be one Module Sub Group. This is the Model.

Module Definition

Multidim: Measure Group

Tabular: Table

The Module Definition results in a Fact table/view in the data warehouse based on one or more Data Source Tables. Column based Business Logic can be added to the resulting  Fact table/view. You can decide how Fact tables are created, selecting if you want view or table, aggregation, partitioning etc.

The Fact result can be linked to different Dimensions. There are different usage options that decides binding types. If a Module Definition uses a Dimension, it will result in a shared Dimension in the Module Group (by SSAS design).

For Multidimensional SSAS, this results in Measure Group. Additional Business Logic like MDX based measures, dimensions or KPIs can be added.

For Tabular SSAS, this results in Table. Additional Business Logic like calculated columns, calculated measures and KPIs can be added. Both dimensions and fact based tables will be tables. So when you are using a dimension it will also be a table (measure group / module definition).

From PS 6.4 release 7, Module Sub Groups and Module Definitions can be enabled/disabled. Disabled definitions will not be processed in the database or SSAS. The functionality is added to ease developent and testing of new functionality.

When to use Multidimensional or Tabular SSAS databases

In addition to Multidimensional SSAS databases, Profitbase Studio 6 can also produce Tabular SSAS databases.

Tabular SSAS databases was introduced in MS SQL 2012. It has focus on tables and these are stored in SSAS server’s memory. The Tabular SSAS server is a separate installation, and can not be combined with Multidimensional SSAS servers (different instances on same server is ok).

A tabular model is a logical representation of tables and relationships for analytical purposes; the model also includes other features like hierarchies of attributes -to provide a richer drill-up and drill-down experience-, like perspectives -to simplify or focus the model into a smaller portion of it-, like Key Performance Indicators and many other features included.  

Compared to multidimensional models, the tabular model is normally faster, but it requires enough RAM since it is a In-memory implementation.