wizard at 04h36
09
Dec
2010
How to handle Large dimensions 35M records
Hi all.
I have a dimension with 35+ million records as compared to 225 Million in the fact table. I am not sure about the kind of penalty we will have to pay for such a big dimension. Here is summary regarding this dimension.
This dimension is derived from a transactional table and provides information about the operator entering the data. because this dimension provides name of operator for each customer transaction
Hi all.
I have a dimension with 35+ million records as compared to 225 Million in the fact table. I am not sure about the kind of penalty we will have to pay for such a big dimension. Here is summary regarding this dimension.
This dimension is derived from a transactional table and provides information about the operator entering the data. because this dimension provides name of operator for each customer transaction
About
This topic belongs to the forum
Data Warehousing and Business Intelligence based on dimensional modeling and the Kimball Lifecycle.
- Numbers of topics : 1858
- Numbers of messages : 8714
- Numbers of users : 3801
- Numbers of points : 1672
Similar topics
Can't find much about this topic anywhere else so hopefully someone can help me.
Our warehouse has late arriving dimensions for an Employee. Their department changes, for example, can be backdated in the systems and so we have to account for this and
I may be misguided in my attempt to make a dimensional model here, but I will explain the scenario. We provide a value add service in the supply chain business...in this case by depicting a scorecard of the accuracy of vendors' product sizing
Hello, all. This is my first time working on a dimensional model and I have some questions regarding multivalue dimensions.
I am modeling our Remedy trouble ticket process and was settling on the grain being each individual ticket. The problems come in
Dear Kimball Group, we are using the Kimball BUS Architecture method with SQL Server 2005, SSIS, SSAS, ProClarity, PPS, and MOSS.
I am at a clients site that is using Full Refresh process for building 3 data marts so far every night. We are trying to
Hi All,
Our OLTP system supports effective dated concept. So users can enter Future Dated Rows also. And in our Warehouse we have both Type1 Dimesnions and Type2 Dimensions.
When loading the data to Type1 dimesnions, if we load future dated row
Forums from same category
Free forum : hi. Free forum : 2709rsgamboa6219. Free forum,
LEGO Island Discussion, modding, news and more!
Free forum : Forum IT Teknik Komputer dan Jaringan SMKN 1 SLAWI
Techy Boards, a growing technology discussion forum! For fans of nintendo, xbox, playstation or anything else!
HmongThoobNtiajTeb. com/
Search
Informations
10 Replies For the topic :
"How to handle Large dimensions 35M records"
This topic has been viewed 1212 times.
Last message :
09/12/2010 at 04h36 by "wizard"






