Dimensional Modelling issue

Hi,
I am working with Stock Exchange data, as per the availability of data, I found 2 dimensions that is
*(1)Time*
*(2)Company*
In my fact table, some of the fact(measures) are changing based on Date(Day) and some of the them are changing based on Time
My questions:
[1] : Can a dimension model have only 2 dimensions ?
[2] : Can I make 2 fact tables, Fact-1 will store measures based on the Date(Day) and Fact-2 will store measures based on the Time ?
Please share your valuable suggestions..
Thanks.
Edited by: 952012 on Feb 14, 2013 1:19 AM
Edited by: 952012 on Feb 14, 2013 1:51 AM

For your questions:
1->Yes, there is no restrictions. Make sure a dimension is joined to any other object. It can be self join using Alias.
2->Creat a logical fact able in BMM and add DayFact and TimeFact as logical sources and set proper content levels if needed.
Since you are going with 2 different granularity, for time you might need a new dimension table as good as W_DAY_D interms minutes.
I think you might need it for analysis based on time and this also helps you to roll up to the day level.
Generally 20130214 is surrogate key for w_day_d for today's record, similarly for Time level you have to go for each minute like
1-->00:01 AM
2
3
60-->01:00AM
101-->01:01AM
.... like that to cover 23:59 PM
Let me know if need more info.
If helps mark

Similar Messages

How to include Abbreviations in Dimensional Model

Dear All,
The question is basically related to modelling but as I am using OWB for this, I am posing the question here.
I have to migrate a HR database from relational model to dimensional model. I have the following situation.
There is a table which has two columns i.e. Country_cod, and country_name like UK- United Kingdom, US - United States. Then in the database where ever it is needed to use information about the country, the country_cod is used. I want to migrate the database to dimensional model, This table does not relate to any other table directly, like a foreign key relationship.
How should I deal with this situation?
Comment please....
regards

You can put your Javascript code in the Onmouseover property of the column.
I don't have the Javascript code for changing the color but for example the following will pop up an alert
<af:outputText value="#{row.DepartmentId}" onmouseover="alert(\'Unload event fired!\')">

Are there any (dis)advantages in building a universe on fully normalized tables instead of building dimensional model/tables and then universe on top of them?

Hello,
I’m hoping someone can help me with understanding advantages and disadvantages if we want to build a universe on top of a fully normalized tables, compared to using a dimensional model with star schemas.
I’ve read some discussions here that say that it is possible to create a universe on top of normalized tables. Then, can we avoid building of dimensional tables (a data mart), and just use normalized tables? I would say that it is easier to use star schema dimensions and facts tables to build a universe, but our end users might ask “why do we have to go through building a dimensional data mart, if we can have same reports with hierarchies and drill-down functionality based on a universe built on top of our already existing normalized tables?”
Can you point me to some established best practices regarding using normalized tables to build a universe? Any documents with some examples for this?
Any expected difficulties during design/development phase of our universe, related to using normalized tables?
Any expected performance degradation if we use normalized tables compared to using dimensional tables?
Can I build universe more easily if I transform (modify) our normalized model (by using alias tables and views) to look like snowflake model?
I’m using BOE XI 3.1, tables are in Oracle 11.2.
Thank you

Few Disadvantages that I usually face when building universe on Normalized tables,
1. Performance - Read operations have to suffer because indexing strategies do not go well with table joins
2. Derived Tables - Due to complex Queries/ Logic, most of the time, end-up creating derived tables, which doesn't use back-end table indexes and slows down the report runtime.
3. Normalized table/ Transaction tables may not always have proper cardinality and often results in Cartesian products
4. Normalized tables may not have tight referential integrity and may have to join more than one column and join on varchar, etc whereas, good Dimensional model datawarehouse will have proper keys/ integer joins and not always necessary to join on multiple fields
5. Often deal with Fan and Chasm Traps
6. Dealing with Database fields with nulls, blanks, date in numeric format, etc.,
7. No Facts, Dimensions separated and most of the time they are in same table
and More...
If performance is not a matter and building Datawarehouse is a big deal, then I will start building Universe on normalized tables by having the database diagram as reference for Joins, contexts, etc
Note: After dealing with universes based on normalized tables for few years (by creating views, complex sql queries data loading to tables and unv on these tables, derived tables), I ended up creating star-schema dimensional model (couple of months extra ETL work), users/ developers felt lot better when they have to create standard/ ad-hoc reports and they are super fast compared to previous universes.

Download IBM Book on Star Schema Design (Dimensional Modeling)

Hello Friends,
You can download an IBM Book on Dimensional Modeling from the following link:
http://www.redbooks.ibm.com/redbooks.nsf/e9abd4a2a3406a7f852569de005c909f/e235dc46161249d38525703e00036135?OpenDocument
The Book is very well explained.

Dear Krish,
Please try this link and let me know if you can open.If not I will email you the Book:
http://www.redbooks.ibm.com/abstracts/sg247138.html?Open
My Email is [email protected]
Thanks
Dave

Download Dimensional Modeling Book (Star Schema Design Book)

Hello Friends,
You can download an IBM Book on Dimensional Modeling from the following
link:
http://www.redbooks.ibm.com/abstracts/sg247138.html?Open
This is an excellent IBM Redbook on Data warehouse design and
Dimensional Modeling design.
Great to read,
Dave

Dear Krish,
Please try this link and let me know if you can open.If not I will email you the Book:
http://www.redbooks.ibm.com/abstracts/sg247138.html?Open
My Email is [email protected]
Thanks
Dave

Porblem with Dimensional modeling

Hi everybody;
I'm new in datawarehousing.
I want to create a datamart about road accident. I have a very simple E/Rship mode :
drivers
1,1
|
|
|
1,N
|
vehicules 1,1-------1,N-accient-1,N ------- 1,1- victime
|
1,1
|
|
|
1,N
|
cause_accident
My physical model :
table cause_accident(code_cause,description,categrie_cause);
table accident (code_accident*,date_accident,region,number_of_victimes,code_cause**);
table vehicule (matricule*,type_vehicule,code_accident**);
table victime (num_victim*,name,age,sexe,code_accident**);
table driver (num_driver*,name,age,sex,code_accident**);
* :primary key
**:foreing key
So I want to create a datamart about raod accident to be able to get some statistics like :
-number of accident per month, year...(time)
-number of victims per month, year...(time)
-number of accident per region
-number of victims per region
-number of accident per vehicule type
-number of accident per victime sex
-number of accident per victime age
-number of accident per driver sex
-number of accident per driver age
I have the fact table "accident"
dimensional tables : times,region
My question is :
how to have the others dimensional tables because we have 1,N (many to many) relation between accident and: driver,victime and vehicule? Really it's not clear for me at all !!!!
Plz I need for your help .
Thank you at advance

If you're new to dimensional modeling I'd suggest the following site:
http://www.kimballgroup.com/html/articles.html
Also worth picking up Ralph Kimball's Data Warehousing book.
Without thinking about this too much, maybe the granularity of the Fact table is per Driver/Vehicle, an Accident dimension can then be used to link the rows that were involved in the accident.
Cheers
Si

Problem with dimensional modeling

Hi everybody;
I'm new in datawarehousing.
I want to create a datamart about road accident. I have a very simple E/Rship mode :
drivers
1,1
|
|
|
1,N
|
vehicules 1,1-------1,N-accient-1,N ------- 1,1- victime
|
1,1
|
|
|
1,N
|
cause_accident
My physical model :
table cause_accident(code_cause,description,categrie_cause);
table accident (code_accident*,date_accident,region,number_of_victimes,code_cause**);
table vehicule (matricule*,type_vehicule,code_accident**);
table victime (num_victim*,name,age,sexe,code_accident**);
table driver (num_driver*,name,age,sex,code_accident**);
* :primary key
**:foreing key
So I want to create a datamart about raod accident to be able to get some statistics like :
-number of accident per month, year...(time)
-number of victims per month, year...(time)
-number of accident per region
-number of victims per region
-number of accident per vehicule type
-number of accident per victime sex
-number of accident per victime age
-number of accident per driver sex
-number of accident per driver age
I have the fact table "accident"
dimensional tables : times,region
My question is :
how to have the others dimensional tables because we have 1,N (many to many) relation between accident and: driver,victime and vehicule? Really it's not clear for me at all !!!!
Plz I need for your help .
Thank you at advance

If you're new to dimensional modeling I'd suggest the following site:
http://www.kimballgroup.com/html/articles.html
Also worth picking up Ralph Kimball's Data Warehousing book.
Without thinking about this too much, maybe the granularity of the Fact table is per Driver/Vehicle, an Accident dimension can then be used to link the rows that were involved in the accident.
Cheers
Si

Dimensional Modeling Question

Hello:
I am new to dimensional modeling and trying to design a model based on the existing OLTP system.
Below are the links to ERDs for existing OLTP system and a dimension model that I have developed. Can someone expert in this area take a quick look and offer me suggestions please? It won't take much time as the model is simple. I am especially worried about the inclusion of bridge table STORE_DEPARTMENT in the model and the dimension tables referencing other dimension tables. Is this normal or I am doing it wrong? I am trying to check if the model can answer some of the DSS questions but your suggestions would really help me if I am going in a wrong direction.
Thanks in advance for your help :)
Regards,
Ramesh

Hi,
There is a trade off on the availability and the Complex analytics.
A star schema is good if you have the functional requirements really simple. Like the dimension is not SCD Type2 (slowly changing dimension) and you don't need to do "AS IS" vs "AS WAS" reporting.
In modern Analytics in any domain dimensions are SCD Type 2 as business keep on evolving. In a star schema structure this will cause explosion of data if there are frequent changes at the higher levels of the dimensional hierarchy. That anyway will hit the performance.
As far as my experience goes, at the data model level it is better to have snow flaked dimensions. and while managing the metadata (in a BI reporting tool) you can consolidate the snowflaked dimensions in star schema structures. That will make ah hoc analytics much simple for the business users.
A lot of performance measure can be taken to improve the end user experience.
In short the trend in BI analytics demands to have a snowflaked structure rather than a simple star schema structure.
Hope this helps.

Designing Dimensional Model from Reports

I'm currently desiging a data warehouse for our project. My problem is that we do not have access to the source system. The only thing we are provided with is the data feeds that are generated by the current reporting system. This is causing me a great deal of headach b/c reports do not give you an entire picture of what the source system. Since reports only display data based on how it is developed, it is difficult to come up with an efficient design. My question is has anyone designed a dimensional model using only Reports as the source?

Hi there,
The short answer to your question is 'no'
A longer answer is 'Surely it is possible to get a copy of the source schema definition even if it is not possible to get access to the source system?'
Stuart

Excellent Dimensional Modeling /star Schema Book by IBM for free downlaod

Hello Friends,
You can download an IBM Book on Dimensional Modeling from the following link:
http://www.redbooks.ibm.com/abstracts/sg247138.html?Open
This is an excellent IBM Redbook on Data warehouse design and Dimensional Modeling design.
Great to read,
Dave

Dear Krish,
Please try this link and let me know if you can open.If not I will email you the Book:
http://www.redbooks.ibm.com/abstracts/sg247138.html?Open
My Email is [email protected]
Thanks
Dave

Dimensional Modeling on SAP Hana

Hello,
I am a newbie on SAP hana, so need help from experts / gurus.
Imagine the following Scenario ---> Oracle ERP is the source System and we want to build a Analytic Solution on Hana. Also assume that tables can be replicated into SAP Hana
Questions
1)For any kind of reporting / Analytics? Should we build a traditional Datawarehouse on Hana with all the features found in a star schema like surrogate keys, conformed facts and dimensions etc? or use only attribute views / analytical views provided as default and build datawarehouse model on top of this? In the second case, do we still need surrogate keys or how can we merge slowly changing dimensions?
2)Where can be push the transformation logic? Into ETL tool or use Hana provided sql script? and also where do we do this transformation, outiside hana where we do all transformations and load only data into normolized format? or within hana using scripts?
3) In any case is dimensional modeling really required on Hana? if not how can we map business process and do analysis on them? is it by means of only the views provided by Hana?
Your help is much appreciated.
Thanks!

Hi Rajiv,
I'm no expert either and am just beginning to learn HANA, but here are my thoughts (community, please correct me if I am mistaken.):
1. HANA leverages existing data modeling theories, such as the entity relationship model. This model is simply a way of organizing tables in a way that makes sense for reporting. For example, the star schema, optimized for analytical reporting. The HANA view is similar to a universe, it allows the end user to connect to it from their BI tool. In the background, the modeler still needs to pull in tables, create joins, leverage primary and foreign keys, etc. So in short, traditional modeling practices and theories still come into play.
2. If extracting and transforming data using SAP's Data Services, the transformation of data will happen in HANA, using the Data Quality Management GUI.
Just as a side note, HANA has 3 methods of extracting
data:
Data Services
SAP Replication
Server
SAP Landscape
Transformation
3. Yes, dimensional modeling is still required. At the end of the day, HANA is still a database. We
haven’t changed the theory of data modeling, it still needs to happen, our approach is just different.
Hope that helps.
Kyle

Views in Dimensional Modelling

Hi
I need info on roles of views in dimensional modelling.,I have searched for this but no luck,,
Can anyone help me in this regard?

Are you looking to create views on Dimension model structure?
Yes. Dimension model structure are oracle tables. You can create view/synonym etc.
I hope this help.

Designer - Dimensional modeling

Can Designer do Dimensional modeling ???
Welcome replies directly to my personal email.
Thanks!

Hi Rajiv,
I'm no expert either and am just beginning to learn HANA, but here are my thoughts (community, please correct me if I am mistaken.):
1. HANA leverages existing data modeling theories, such as the entity relationship model. This model is simply a way of organizing tables in a way that makes sense for reporting. For example, the star schema, optimized for analytical reporting. The HANA view is similar to a universe, it allows the end user to connect to it from their BI tool. In the background, the modeler still needs to pull in tables, create joins, leverage primary and foreign keys, etc. So in short, traditional modeling practices and theories still come into play.
2. If extracting and transforming data using SAP's Data Services, the transformation of data will happen in HANA, using the Data Quality Management GUI.
Just as a side note, HANA has 3 methods of extracting
data:
Data Services
SAP Replication
Server
SAP Landscape
Transformation
3. Yes, dimensional modeling is still required. At the end of the day, HANA is still a database. We
haven’t changed the theory of data modeling, it still needs to happen, our approach is just different.
Hope that helps.
Kyle

Dimensional modeling scenario

Hi Experts,
I am having a requirement to do dimensional datamodel for a datawarehouse for the below scenario. Please provide me your suggestions. How many dimensions and facts which i should consider for this? Given below is my requirements.
Percentage and Numbers of care plans due for review, indate or expired
Analysis by home, keyworker, client
Drill down to home by client
Drill down to keyworker by client
Drill down to client
Source OLTP Tables
Patient : (PatientInfo)
=========
clientName
clientAdress
Age
Staff: (StaffInfo/Keyworker)
============
StaffName
StaffDept
DOB
Careplan:(This table will holds Patient Careplans)(1:M)
=========
Expected Outcome (Expected Result of this actionplan)
Current Situation (Current condition of patient)
Action (what is the action taken for the result)
Start Date (patient start)
review Date (for every care plan there will be review date and on that date this record will expire and create a new record with the current situation)
EndDate (End date of patient)
Keyworker(Staff which is in primary charge for this patient- A staff can be keyworker for multiple patients)
thanks
MUS

Hi Rajiv,
I'm no expert either and am just beginning to learn HANA, but here are my thoughts (community, please correct me if I am mistaken.):
1. HANA leverages existing data modeling theories, such as the entity relationship model. This model is simply a way of organizing tables in a way that makes sense for reporting. For example, the star schema, optimized for analytical reporting. The HANA view is similar to a universe, it allows the end user to connect to it from their BI tool. In the background, the modeler still needs to pull in tables, create joins, leverage primary and foreign keys, etc. So in short, traditional modeling practices and theories still come into play.
2. If extracting and transforming data using SAP's Data Services, the transformation of data will happen in HANA, using the Data Quality Management GUI.
Just as a side note, HANA has 3 methods of extracting
data:
Data Services
SAP Replication
Server
SAP Landscape
Transformation
3. Yes, dimensional modeling is still required. At the end of the day, HANA is still a database. We
haven’t changed the theory of data modeling, it still needs to happen, our approach is just different.
Hope that helps.
Kyle

Powerpivot 2013 doesn't work on Excel 2013 / Office 365: data model issue

Hi guys
I recently upgraded my Office 2010 to Office 365, with Excel 2013. Before installing Office 365 I uninstalled Office 2010. I'm running Windows 8 64 bits.
I have the Powerpivot 2013 add-in, I can activate it without any issue. However when I click on "manage" on any spreadsheet (including new empty ones) I have an error "We
couldn't load the Data Model. This may be because the Data Model in this workbook is damaged.", followed by "PowerPivot is unable to load the Data Model".
I tried to repair the installation to no avail. I tried to launch excel in admin mode, nothing better.
This issue seems to be shared by some other people on this forum but
with no satisfactory answer so far.
I had a SQL server 2012 plugin installed previously which I uninstalled as well, but no change.
Would you think of something else?
Thanks

Hi lourson,
Someone work out this issue to stop the Tabular Model instance. Please take a look at the following blog:
PowerPivot 2013 Error: Data Model Damaged:
http://www.mssqlgirl.com/powerpivot-2013-error-data-model-damaged.html
For more information, please see the same issue at Connect site:
https://connect.microsoft.com/SQLServer/feedback/details/780949/powerpivot-couldnt-load-data-model-when-ssas-tabular-instance-is-running#details
Hope you can solve this issue on your new work environment.
Regards,
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Dimensional Modelling issue

Similar Messages

Maybe you are looking for