Dear Srikanth,

Hope you are doing well.

Thanks for raising a request, we are glad to assist you.

Q. What is the difference between Conformed and Role Playing dimensions? I failed to understand the difference between these 2 types of dimensions after watching the recording. Please advise.


Conformed dimension means internally its the same dimension in database which will be utilized in multiple data marts (cubes) as dimensions. For example you'll have Customer dimension table in database. You will be sharing the same table across multiple cubes like customer detail analysis cube, sales info cube etc

Role playing dimension is within the same cube dimension would be utilized multiple times. Best example is date dimension. In case of order facts you will have multiple dates associated like OrderDate,ShippedDate,DeliveryDate etc. So based on relationship we will have multiple dimensions within same cube as DeliveryDate,OrderDate etc which will all point to the same dimension table. So its same dimension repeated multiple times within the same cube

More details:

A database dimension is a collection of related objects, called attributes, which can be used to provide information about fact data in one or more cubes. What we created in BIDS is database dimension. For example, typical attributes in a product dimension might be product name, product category, product line, product size, and product price. These objects are bound to one or more columns in one or more tables in a data source view.

Cube dimension is an instance of a database dimension in a cube is called a cube dimension and relates to one or more measure groups in the cube. A database dimension can be used multiple times in a cube. Those referenced and renamed for purpose database dimension is role-playing dimension. For example, a fact table can have multiple time-related facts, and a separate cube dimension can be defined to assist in analyzing each time-related fact. However, only one time-related database dimension needs to exist, which also means that only one time-related relational database table needs to exist to support multiple cube dimensions based on time.