I am rebuilding a factual fat table from a transaction table. Organization, status, service, service action, delivery date, etc. are clearly shared recessions. However, I am working on 2 issues:
-
On the transaction table, there are free form entry fields for prices such as phone, email, chkbxRequestReceipt, they are all directly related to TransactionKey if I draw these fields in my own dim from the fact table, so it creates a 1-1 dim-related relationship that is not right.
-
The service is dim dim 1 field on the fact table but then split into 3 different haze tables. This was done because the services were not shared nearly the general area. There is 1 transaction for each service action. So 3 service table = the sum of rows in the total rows of the transaction table.
Can someone recommend this model in the best possible way?
-
You can call (e-mail), chkbxRequestReceipt (or multiple dzenet) Can consider dimension). A dimensional dimension is a dimension without a dimension table. You have dimension dimensions when there is a transaction level grain in the facts table.
-
For the three tables for service action , I would suggest that they be put in the same dimension table, but I think your There will be a table with several numbers, if you manually write your report then there are no problems in the three tables, but if you use a tool that automatically generates a SQL code for a one-dimensional model Sub Industry does, then you probably need a dimension table.
You can also think of three different dimensions that share the same columns on the fact table, it will work, but it can be a little confusing for business users. Anyway, if they can make their reports anyway, in this case, you will need to create a forward dimension AllSerivceAction , if you need to create a report where you want to show all calls and about it Also info ServiceAction
No comments:
Post a Comment