<?xml version="1.0" encoding="iso-8859-1"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:dc="http://purl.org/dc/elements/1.1/">
	<channel>
		<title>Dimensional Modeling and Data Architecture</title>
		<link>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/-t1.htm</link>
		<description></description>
		<lastBuildDate>Sun, 22 Nov 2009 01:28:14 GMT</lastBuildDate>
		<ttl>10</ttl>
		<image>
			<title>Dimensional Modeling and Data Architecture</title>
			<url>http://kimballgroup.com/images/KGlogoBasic.gif</url>
			<link>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/-t1.htm</link>
		</image>
		<item>
			<title>Surrogate key for different granularities</title>
			<link>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/surrogate-key-for-different-granularities-t356.htm</link>
			<dc:creator>saeidziaei</dc:creator>
			<description>Hi

In a life insurance context, I have products and benefits tables and also another table that specifies their relation. I thought combining them all in a single dimension is not a bad idea but I will have different facts which should point to either benefit or product. Which surrogate key should I use in my fact tables?



I suppose this most be very common problem but have not been able to find an answer on the net. Like if you had sale fact on day grain and budget on the month grain,  ...</description>
			<category>Dimensional Modeling and Data Architecture</category>
			<pubDate>Sun, 22 Nov 2009 01:28:14 GMT</pubDate>
			<comments>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/surrogate-key-for-different-granularities-t356.htm#1449</comments>
			<guid>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/surrogate-key-for-different-granularities-t356.htm</guid>
		</item>
		<item>
			<title>Flat Table vs star schema</title>
			<link>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/flat-table-vs-star-schema-t314.htm</link>
			<dc:creator>bi_at_nj</dc:creator>
			<description>We hear a lot of BI implementations using star schema. (with few dims snowflaked sometimes )



Why not choose a flat table with all data put together instead of a star schema?

(well , this question may seem strange, but please help me out here)



Few answers which I have answered to myself are:

* Data retrieval with star joins perform better in star schema for the sake of reporting.

* It all depends on the volume.



What other possible answers are out there for FlatTable Vs StarSchema?



-  ...</description>
			<category>Dimensional Modeling and Data Architecture</category>
			<pubDate>Sat, 31 Oct 2009 04:38:33 GMT</pubDate>
			<comments>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/flat-table-vs-star-schema-t314.htm#1329</comments>
			<guid>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/flat-table-vs-star-schema-t314.htm</guid>
		</item>
		<item>
			<title>Dimensions Directly Tied to Facts vs. Snowflaking</title>
			<link>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/dimensions-directly-tied-to-facts-vs-snowflaking-t335.htm</link>
			<dc:creator>kbarrett</dc:creator>
			<description>Hi all,



Thanks in advance for your input on this.

We are in the midst of a building out a portion of our data warehouse. The example here has to do with insurance data. Hopefully the discussion can be abstracted to a more generic modeling level.



We are looking at two options.



Option 1 (see image) joins a dimension directly to the fact table



http://img691.imageshack.us/i/dimproductoption1.png/







Option 2 (see image) snowflake the table allowing for a view of the  ...</description>
			<category>Dimensional Modeling and Data Architecture</category>
			<pubDate>Wed, 11 Nov 2009 00:58:26 GMT</pubDate>
			<comments>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/dimensions-directly-tied-to-facts-vs-snowflaking-t335.htm#1379</comments>
			<guid>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/dimensions-directly-tied-to-facts-vs-snowflaking-t335.htm</guid>
		</item>
		<item>
			<title>Dimensional Attributes</title>
			<link>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/dimensional-attributes-t343.htm</link>
			<dc:creator>Arvind</dc:creator>
			<description>Hello,



I have a requirement where a dimension can have potentially hundreds of attributes that can change over a period of time. The end reporting requirement is that we should be able to run the report where we select a combination of attributes.



An example may help. In the Insurance company design, I have a Policy Dimension and then an Insured Item Dimension which are linked in a fact table. Now the Insured Item Dimension can have several attributes. For example, if the insured item  ...</description>
			<category>Dimensional Modeling and Data Architecture</category>
			<pubDate>Sun, 15 Nov 2009 15:38:20 GMT</pubDate>
			<comments>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/dimensional-attributes-t343.htm#1402</comments>
			<guid>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/dimensional-attributes-t343.htm</guid>
		</item>
		<item>
			<title>Eliminate Date Dimension Surrogate Key</title>
			<link>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/eliminate-date-dimension-surrogate-key-t334.htm</link>
			<dc:creator>juz_b</dc:creator>
			<description>We have always been using a sequential surrogate key for all our Dimension tables, including the Calendar Dimension.



There is also a different school of thought (only for Calendar Dimension) where instead of using sequential keys, replace it with a smartkey in the format of YYYYMMDD.  I can appreciate this design since Calendar Days are always unique and sequential.  Also note that this is the BASE CALENDAR, there are no Fiscal Attributes at all.



Recently we came across a recommendation  ...</description>
			<category>Dimensional Modeling and Data Architecture</category>
			<pubDate>Fri, 06 Nov 2009 20:57:58 GMT</pubDate>
			<comments>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/eliminate-date-dimension-surrogate-key-t334.htm#1373</comments>
			<guid>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/eliminate-date-dimension-surrogate-key-t334.htm</guid>
		</item>
		<item>
			<title>difference between alias and duplicate tables in OBIEE</title>
			<link>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/difference-between-alias-and-duplicate-tables-in-obiee-t350.htm</link>
			<dc:creator>Jaswanth</dc:creator>
			<description>Tell me about these alias and duplicate tables in repository of obiee and how they differ from one another and when we work on these tables</description>
			<category>Dimensional Modeling and Data Architecture</category>
			<pubDate>Tue, 17 Nov 2009 05:10:05 GMT</pubDate>
			<comments>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/difference-between-alias-and-duplicate-tables-in-obiee-t350.htm#1416</comments>
			<guid>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/difference-between-alias-and-duplicate-tables-in-obiee-t350.htm</guid>
		</item>
		<item>
			<title>Alternative views of data</title>
			<link>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/alternative-views-of-data-t351.htm</link>
			<dc:creator>jchamizo</dc:creator>
			<description><![CDATA[Hi!!!
<br />

<br />
I have some data that have a particular granularity that I store in our Data Mart, but when I have to do most of the reports using the Data Mart I have to use a different granularity. For the input granularity I am using a Hierarchical Dimension, but in the output another Hierarchical Dimension must be used. How can I model this situation?
<br />

<br />
Thanks and best regards,
<br />
jchamizo]]></description>
			<category>Dimensional Modeling and Data Architecture</category>
			<pubDate>Tue, 17 Nov 2009 15:22:27 GMT</pubDate>
			<comments>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/alternative-views-of-data-t351.htm#1417</comments>
			<guid>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/alternative-views-of-data-t351.htm</guid>
		</item>
		<item>
			<title>Rapidly changing Monster dimension...</title>
			<link>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/rapidly-changing-monster-dimension-t352.htm</link>
			<dc:creator>VK</dc:creator>
			<description>Hi Everyone,



I have a list of more than 300 attributes, which are actually part of the fact table….(basically ..these values changes for each transaction level record in fact but belongs to a single dimension).

that lot contains more than a 100 date attributes,.. around a 50 monetary values, more than 10 comments…n some flags.



If I put Date surrogate keys into fact table for all these date values …it definitely clutters…the fact.

Will that affect the performance????..the idea of  ...</description>
			<category>Dimensional Modeling and Data Architecture</category>
			<pubDate>Tue, 17 Nov 2009 16:49:52 GMT</pubDate>
			<comments>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/rapidly-changing-monster-dimension-t352.htm#1419</comments>
			<guid>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/rapidly-changing-monster-dimension-t352.htm</guid>
		</item>
		<item>
			<title>Building a Recruitment and Admissions fact table</title>
			<link>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/building-a-recruitment-and-admissions-fact-table-t354.htm</link>
			<dc:creator>kikesegarra</dc:creator>
			<description>Hi



 I'm currently working in a Recruitment and admissions data mart for a university. Right now I'm designing the student fact table.  In this fact table I want to track the prospective student events during the recruitment, application, and admission process. I'm not sure if I have to build a separate fact table for the prospect student because this is a process that involve different contact dates with the prospective student, and the application and admission part has only one or two  ...</description>
			<category>Dimensional Modeling and Data Architecture</category>
			<pubDate>Tue, 17 Nov 2009 19:50:57 GMT</pubDate>
			<comments>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/building-a-recruitment-and-admissions-fact-table-t354.htm#1421</comments>
			<guid>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/building-a-recruitment-and-admissions-fact-table-t354.htm</guid>
		</item>
		<item>
			<title>Cost plans for projects - One fact table or several fact tables?</title>
			<link>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/cost-plans-for-projects-one-fact-table-or-several-fact-tables-t353.htm</link>
			<dc:creator>bustaliz</dc:creator>
			<description>Hi, 

I'm currently struggling with my Dimensional Model. It is about projects with their related cost plans. Every project starts with an initial cost plan (called WIPL), the project is saved as version 0 and the WIPL attribute and the ACTUAL attribute in the database is set to Y. If the cost plan is updated in the course of the year the project is saved as a new version, here it would be version 1 and the ACTUAL attribute in the database is set to Y.  The ACTUAL attribute of version 0 is set  ...</description>
			<category>Dimensional Modeling and Data Architecture</category>
			<pubDate>Tue, 17 Nov 2009 18:37:40 GMT</pubDate>
			<comments>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/cost-plans-for-projects-one-fact-table-or-several-fact-tables-t353.htm#1420</comments>
			<guid>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/cost-plans-for-projects-one-fact-table-or-several-fact-tables-t353.htm</guid>
		</item>
		<item>
			<title>The best design for EDW to cover common and un-common processes</title>
			<link>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/the-best-design-for-edw-to-cover-common-and-un-common-processes-t348.htm</link>
			<dc:creator>Niaz</dc:creator>
			<description>Thanks for any help, suggestion, advise, etc. in advance...



We have a big initiatives to integrate 20 JDEdward libraries (companies) into one through Oracle Enterprise One application. The OLTP will stay on Oracle Database and data will be migrated to new structure. There will be common processed for module such as HR, financial, Maintenance and Purchasing. However there will be many un-common processes such as Sales, Production, Inventory, etc. For Reporting, we will have Enterprise Data  ...</description>
			<category>Dimensional Modeling and Data Architecture</category>
			<pubDate>Mon, 16 Nov 2009 19:05:51 GMT</pubDate>
			<comments>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/the-best-design-for-edw-to-cover-common-and-un-common-processes-t348.htm#1412</comments>
			<guid>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/the-best-design-for-edw-to-cover-common-and-un-common-processes-t348.htm</guid>
		</item>
		<item>
			<title>Schema Roadblock: Dimension vs Fact [Dimensions w/FKs to other Dimensions?]</title>
			<link>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/schema-roadblock-dimension-vs-fact-dimensions-w-fks-to-other-dimensions-t347.htm</link>
			<dc:creator>riafan</dc:creator>
			<description>Hello,

  I'm new to DM, I've picked up Kimball's DW Toolkit and DW ETL Toolkit - both great books.  



  I'm designing a simple datawarehouse for eduction (K-12) and ran into a modeling question.  I'm designing the portion pertaining to [homework] assigments.  A teacher creates an assignment and scores each student on the assignment.  So my thought was simple, an Assignment Dimension and an Assignment Score Fact.



Here's where I'm hung up...  The assignment has references to other dimensions,  ...</description>
			<category>Dimensional Modeling and Data Architecture</category>
			<pubDate>Mon, 16 Nov 2009 15:21:34 GMT</pubDate>
			<comments>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/schema-roadblock-dimension-vs-fact-dimensions-w-fks-to-other-dimensions-t347.htm#1406</comments>
			<guid>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/schema-roadblock-dimension-vs-fact-dimensions-w-fks-to-other-dimensions-t347.htm</guid>
		</item>
		<item>
			<title>Facts at different levels.</title>
			<link>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/facts-at-different-levels-t346.htm</link>
			<dc:creator>VK</dc:creator>
			<description>Hi Everyone,

The data I have has no perticular grain statement on which I can base my model..



 Can someone suggest a better design for this scenario,



Simplified version is,...



I have 2 dimensions 

1) Property..  Heirarchy is Site -&gt; Building -&gt; Floor.

2) Account (No heirarchies)



The account values are available at different levels...(for some of the accounts it is at building level...and for some it is Floor level)

There are some buildings with no floors.



I  ...</description>
			<category>Dimensional Modeling and Data Architecture</category>
			<pubDate>Mon, 16 Nov 2009 14:19:47 GMT</pubDate>
			<comments>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/facts-at-different-levels-t346.htm#1405</comments>
			<guid>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/facts-at-different-levels-t346.htm</guid>
		</item>
		<item>
			<title>Guidelines for FACT Table Design for High-Transaction Volume and High # of Measures ...</title>
			<link>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/guidelines-for-fact-table-design-for-high-transaction-volume-and-high-of-measures-t341.htm</link>
			<dc:creator>kminboston</dc:creator>
			<description>Hi All - 



This inquiry could actually be two questions, but the requirement is really presentation of row-wise high volume transactional data in a column-wise (columnar) FACT table.



Here is a sample transactional data set:



Interval Date TimeUnit IDChannelValue7/2/2009 12:00:00.000000 AM 24781143.757/2/2009 12:00:00.000000 AM 24781352.177/2/2009 12:05:00.000000 AM 24781152.357/2/2009 12:05:00.000000 AM 24781351.987/2/2009 12:10:00.000000 AM 24781151.967/2/2009  ...</description>
			<category>Dimensional Modeling and Data Architecture</category>
			<pubDate>Fri, 13 Nov 2009 21:44:50 GMT</pubDate>
			<comments>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/guidelines-for-fact-table-design-for-high-transaction-volume-and-high-of-measures-t341.htm#1398</comments>
			<guid>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/guidelines-for-fact-table-design-for-high-transaction-volume-and-high-of-measures-t341.htm</guid>
		</item>
		<item>
			<title>Proving performance - HELP</title>
			<link>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/proving-performance-help-t339.htm</link>
			<dc:creator>AndyPainter</dc:creator>
			<description>I have an interesting problem, in that i need to be able to build confidence in a client that when the dimensional model has been deployed it will be a much more performant solution that they currently have.  They currently have a copy of a transactional system schema that they query. 



The problem i have is how to demonstrate this, with limited resources.  The proof of concept box i have, has very limited resources and i can't get anywere near live data, or a good representation of what  ...</description>
			<category>Dimensional Modeling and Data Architecture</category>
			<pubDate>Thu, 12 Nov 2009 15:17:48 GMT</pubDate>
			<comments>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/proving-performance-help-t339.htm#1386</comments>
			<guid>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/proving-performance-help-t339.htm</guid>
		</item>
		<item>
			<title>Modeling price information collected at intervals</title>
			<link>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/modeling-price-information-collected-at-intervals-t340.htm</link>
			<dc:creator>jantzen</dc:creator>
			<description>Hi All, I'd appreciate some feedback on a dimensional model for representing prices collected from source websites at varying intervals.



The incoming data is an observation of a price at a given point in time on the website.  We want to be able to link prices back to when the data was collected, and also be able to query for the price that was in effect for a given period.  My thought on how to accomplish this to have two fact tables: the first a transaction fact recording the price observation;  ...</description>
			<category>Dimensional Modeling and Data Architecture</category>
			<pubDate>Thu, 12 Nov 2009 21:01:10 GMT</pubDate>
			<comments>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/modeling-price-information-collected-at-intervals-t340.htm#1392</comments>
			<guid>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/modeling-price-information-collected-at-intervals-t340.htm</guid>
		</item>
		<item>
			<title>Conformed Dimension Partial Set of Attributes</title>
			<link>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/conformed-dimension-partial-set-of-attributes-t337.htm</link>
			<dc:creator>dcow</dc:creator>
			<description>Hi Just looking for some confirmation  that  a dimension with partial attributes  might still be considered conformed.    For eample



A dimension  of  batch



ProdBatch PK

BatchID

Batch Name

Product ID

Product Name

...

at an invoice Fact table level  with a grain of Lineitem  the line item would reference the Prodbatch Surrogate in the batcch dimension





In another datamart Lets Say a Planning datamart   The planning iis conducted  at  the product level



and so my  ...</description>
			<category>Dimensional Modeling and Data Architecture</category>
			<pubDate>Thu, 12 Nov 2009 01:13:42 GMT</pubDate>
			<comments>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/conformed-dimension-partial-set-of-attributes-t337.htm#1382</comments>
			<guid>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/conformed-dimension-partial-set-of-attributes-t337.htm</guid>
		</item>
		<item>
			<title>Inventory Snapshot - GMROI Calculation</title>
			<link>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/inventory-snapshot-gmroi-calculation-t336.htm</link>
			<dc:creator>Sophie</dc:creator>
			<description>We are developing a solution for our company. We currently have a sales cube and we are in the process of building an inventory cube. We are having a design problem in that we are not sure if we should include some of the measures which currently exist in the sales fact table (Qty Sold and Latest Selling Price) in the inventory snapshot table. 



We are thinking of creating a separate cube for inventory and defining GMROI as a linked measure group using both sales and inventory cube.

What's  ...</description>
			<category>Dimensional Modeling and Data Architecture</category>
			<pubDate>Wed, 11 Nov 2009 21:00:13 GMT</pubDate>
			<comments>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/inventory-snapshot-gmroi-calculation-t336.htm#1381</comments>
			<guid>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/inventory-snapshot-gmroi-calculation-t336.htm</guid>
		</item>
		<item>
			<title>Model for storing dimension attributes in multiple languages</title>
			<link>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/model-for-storing-dimension-attributes-in-multiple-languages-t330.htm</link>
			<dc:creator>jefoster</dc:creator>
			<description>We have a traditional dimensional model and are about to add multiple languages to our source systems and need the option of reporting certain dimensional attributes in either the local language or English. Has anyone developed a flexible model for this that would allow adding multiple language versions of attributes without adding columns to the dimension table directly?



2 options I can think of are:



1) An abstracted translation dimension that contains the attribute name, language,  ...</description>
			<category>Dimensional Modeling and Data Architecture</category>
			<pubDate>Thu, 05 Nov 2009 01:29:39 GMT</pubDate>
			<comments>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/model-for-storing-dimension-attributes-in-multiple-languages-t330.htm#1367</comments>
			<guid>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/model-for-storing-dimension-attributes-in-multiple-languages-t330.htm</guid>
		</item>
		<item>
			<title>SCD's and Fact Tables</title>
			<link>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/scd-s-and-fact-tables-t329.htm</link>
			<dc:creator>jimbo1580</dc:creator>
			<description><![CDATA[How do you handle the situation when a conformed dimension is linked to more than one fact table and one fact cares when a particular dimension attribute is changes, but the other does not?  Or when one fact table cares when attribute A changes, but the other fact table cares when attribute B changes?  Does your design or the way you link from the facts to the dimension change at all?
<br />
Thanks]]></description>
			<category>Dimensional Modeling and Data Architecture</category>
			<pubDate>Wed, 04 Nov 2009 15:07:19 GMT</pubDate>
			<comments>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/scd-s-and-fact-tables-t329.htm#1365</comments>
			<guid>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/scd-s-and-fact-tables-t329.htm</guid>
		</item>
		<item>
			<title>Customer Dimension</title>
			<link>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/customer-dimension-t313.htm</link>
			<dc:creator>kenny</dc:creator>
			<description>I am trying to model a Customer Dimension with Educational and Employment details and I want some advice on how to model this scenario

A Customer can have several levels of Education like schooling, college, university, training (one to many realtionship) and

A Customer could have been employed at several places throughout his/her life (one to many realtionship), If I create a record for each level of Education and Employment I would be storing too many records



what is the best way to  ...</description>
			<category>Dimensional Modeling and Data Architecture</category>
			<pubDate>Fri, 30 Oct 2009 22:19:13 GMT</pubDate>
			<comments>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/customer-dimension-t313.htm#1328</comments>
			<guid>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/customer-dimension-t313.htm</guid>
		</item>
		<item>
			<title>Modeling Question - Accumulating Snapshot vs. Event Transactions</title>
			<link>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/modeling-question-accumulating-snapshot-vs-event-transactions-t307.htm</link>
			<dc:creator>jimbo1580</dc:creator>
			<description>I have a business process that has 6 distinct steps from start to conclusion for each instance of the process, we'll call it a case.  Each case has two employees assigned to it, 1 owner and 1 co-owner.  The owner and co-owner each have different responsibilities and each put in work to get the case to move through the process.  The process can take anywhere from 2 months to 2 years to complete.  Since the process can take some time, the owner and/or co-owner can change for a case over time.   ...</description>
			<category>Dimensional Modeling and Data Architecture</category>
			<pubDate>Fri, 23 Oct 2009 14:17:55 GMT</pubDate>
			<comments>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/modeling-question-accumulating-snapshot-vs-event-transactions-t307.htm#1300</comments>
			<guid>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/modeling-question-accumulating-snapshot-vs-event-transactions-t307.htm</guid>
		</item>
		<item>
			<title>Snowflake scenarios</title>
			<link>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/snowflake-scenarios-t318.htm</link>
			<dc:creator>bi_at_nj</dc:creator>
			<description><![CDATA[Had seen a few places where dimensions were snowflaked.
<br />

<br />
But how do we figure out that these snowflaked dimensions are justified?
<br />

<br />
Specify scenarios where snowflaking is acceptable.
<br />

<br />
Thanks in advance,
<br />
bi_at_nj]]></description>
			<category>Dimensional Modeling and Data Architecture</category>
			<pubDate>Sat, 31 Oct 2009 04:48:55 GMT</pubDate>
			<comments>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/snowflake-scenarios-t318.htm#1333</comments>
			<guid>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/snowflake-scenarios-t318.htm</guid>
		</item>
		<item>
			<title>Date Dimension</title>
			<link>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/date-dimension-t290.htm</link>
			<dc:creator>mark.tan</dc:creator>
			<description>Hi All,



I understood Kimball way of implementation Date Dimension table. In a way, the lowest granularity date represent each record, with the following month, quarter and year attribute. However, what happen if the lowest grain of certain fact are at date level? They could be at monthly level, so is it right to tag the fact to the date dimension table using the first day of the month (e.g. 01-12-2008 for Dec 2009)?



If not, can anyone tell me what is the best strategy?



Best Regards,

Mark </description>
			<category>Dimensional Modeling and Data Architecture</category>
			<pubDate>Sat, 10 Oct 2009 07:34:20 GMT</pubDate>
			<comments>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/date-dimension-t290.htm#1241</comments>
			<guid>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/date-dimension-t290.htm</guid>
		</item>
		<item>
			<title>Partitioning Strategy for Fact and Dims in Oracle/DB2/Sybase</title>
			<link>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/partitioning-strategy-for-fact-and-dims-in-oracle-db2-sybase-t326.htm</link>
			<dc:creator>bi_at_nj</dc:creator>
			<description><![CDATA[Please specify the partition strategy you follow in your organization for facts and dims in Ora/Sybase/Db2
<br />

<br />
 Thanks,
<br />
bi_at_nj]]></description>
			<category>Dimensional Modeling and Data Architecture</category>
			<pubDate>Sat, 31 Oct 2009 06:34:00 GMT</pubDate>
			<comments>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/partitioning-strategy-for-fact-and-dims-in-oracle-db2-sybase-t326.htm#1341</comments>
			<guid>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/partitioning-strategy-for-fact-and-dims-in-oracle-db2-sybase-t326.htm</guid>
		</item>
		<item>
			<title>Fact Table Indexing Strategy</title>
			<link>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/fact-table-indexing-strategy-t315.htm</link>
			<dc:creator>bi_at_nj</dc:creator>
			<description>Please explain the indexing strategy which is in use in your organisation for fact tables in your current database(oracle, sybase, db2)



Specify volume as the indexing strategy may be based upon the volume of data.



Is there a well laid out strategy for Indexing for fact tables?



If so, what is it we follow for Fact Tables in Oracle?

and

If so, what is it we follow for Fact Tables in Sybase?

and

If so, what is it we follow for Fact Tables in Db2? </description>
			<category>Dimensional Modeling and Data Architecture</category>
			<pubDate>Sat, 31 Oct 2009 04:41:45 GMT</pubDate>
			<comments>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/fact-table-indexing-strategy-t315.htm#1330</comments>
			<guid>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/fact-table-indexing-strategy-t315.htm</guid>
		</item>
		<item>
			<title>Geospatial Modeling</title>
			<link>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/geospatial-modeling-t328.htm</link>
			<dc:creator>tlfancher</dc:creator>
			<description>Are there any resources I can reference for modeling geospatial data?



In our particular case, we are modeling a pipeline as the basic &quot;fact&quot; where the geographic location is of particular importance.  In addition we need to model the location of attributes of the pipe (size, material, etc.) as well as location of such items as valves, tees, others.  We also need to know attributes of the pipe surroundings: which state, city, does it go through; what is the land use (farm, forest,  ...</description>
			<category>Dimensional Modeling and Data Architecture</category>
			<pubDate>Mon, 02 Nov 2009 13:09:48 GMT</pubDate>
			<comments>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/geospatial-modeling-t328.htm#1345</comments>
			<guid>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/geospatial-modeling-t328.htm</guid>
		</item>
		<item>
			<title>Dimension Table Indexing Strategy</title>
			<link>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/dimension-table-indexing-strategy-t316.htm</link>
			<dc:creator>bi_at_nj</dc:creator>
			<description><![CDATA[Please tell me what kind of indexes you are using in your dimension tables in your organization.
<br />

<br />
I am looking for dimension tables indexing strategy for Sybase, Oracle and Db2.
<br />

<br />
If you have any indexing strategy document for Dimension tables for Oracle, sybase and Db2 that would be helpful.
<br />

<br />
- Thanks in advance,
<br />
nj_at_bi]]></description>
			<category>Dimensional Modeling and Data Architecture</category>
			<pubDate>Sat, 31 Oct 2009 04:44:56 GMT</pubDate>
			<comments>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/dimension-table-indexing-strategy-t316.htm#1331</comments>
			<guid>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/dimension-table-indexing-strategy-t316.htm</guid>
		</item>
		<item>
			<title>Sybase Databases in BI world?</title>
			<link>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/sybase-databases-in-bi-world-t327.htm</link>
			<dc:creator>bi_at_nj</dc:creator>
			<description><![CDATA[What are the most important things that come to mind when you think of Sybase as your playground for building your  Bi / DW application ?
<br />

<br />
Please specify the pros and cons. (you may compare it with either Oracle or Db2 or in general )
<br />

<br />
Thanks,
<br />
bi_at_nj]]></description>
			<category>Dimensional Modeling and Data Architecture</category>
			<pubDate>Sat, 31 Oct 2009 06:36:39 GMT</pubDate>
			<comments>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/sybase-databases-in-bi-world-t327.htm#1342</comments>
			<guid>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/sybase-databases-in-bi-world-t327.htm</guid>
		</item>
		<item>
			<title>Version Controlling your Data models</title>
			<link>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/version-controlling-your-data-models-t325.htm</link>
			<dc:creator>bi_at_nj</dc:creator>
			<description><![CDATA[How do you version control your data models today?
<br />

<br />
Thanks,
<br />
bj_at_nj]]></description>
			<category>Dimensional Modeling and Data Architecture</category>
			<pubDate>Sat, 31 Oct 2009 06:32:29 GMT</pubDate>
			<comments>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/version-controlling-your-data-models-t325.htm#1340</comments>
			<guid>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/version-controlling-your-data-models-t325.htm</guid>
		</item>
		<item>
			<title>eacoe training?</title>
			<link>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/eacoe-training-t324.htm</link>
			<dc:creator>bi_at_nj</dc:creator>
			<description><![CDATA[Can someone tell me if eacoe(.org) training is worth the time and cost? (I have some architecture experience and want to take it to the next level) 
<br />

<br />
Any comments on eacoe training?
<br />

<br />
Thanks
<br />
bi_at_nj]]></description>
			<category>Dimensional Modeling and Data Architecture</category>
			<pubDate>Sat, 31 Oct 2009 06:30:05 GMT</pubDate>
			<comments>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/eacoe-training-t324.htm#1339</comments>
			<guid>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/eacoe-training-t324.htm</guid>
		</item>
		<item>
			<title>Database by name KDB ?</title>
			<link>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/database-by-name-kdb-t323.htm</link>
			<dc:creator>bi_at_nj</dc:creator>
			<description><![CDATA[Is anyone using a database by name KDB ?
<br />

<br />
What are your comments on it ?
<br />

<br />
What ETL tool are you using with it ? Infa? (using ODBC driver? do they have odbc driver for this? )
<br />

<br />
Please specify.
<br />

<br />
Thanks,
<br />
bi_at_nj]]></description>
			<category>Dimensional Modeling and Data Architecture</category>
			<pubDate>Sat, 31 Oct 2009 06:28:29 GMT</pubDate>
			<comments>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/database-by-name-kdb-t323.htm#1338</comments>
			<guid>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/database-by-name-kdb-t323.htm</guid>
		</item>
		<item>
			<title>Specify acceptable Snowflaking scenarios</title>
			<link>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/specify-acceptable-snowflaking-scenarios-t319.htm</link>
			<dc:creator>bi_at_nj</dc:creator>
			<description><![CDATA[Can someone please specify acceptable snowflaking scenarios.
<br />

<br />
- Thanks in advance
<br />
bi_at_nj]]></description>
			<category>Dimensional Modeling and Data Architecture</category>
			<pubDate>Sat, 31 Oct 2009 04:49:54 GMT</pubDate>
			<comments>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/specify-acceptable-snowflaking-scenarios-t319.htm#1334</comments>
			<guid>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/specify-acceptable-snowflaking-scenarios-t319.htm</guid>
		</item>
		<item>
			<title>Sybase Indexes</title>
			<link>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/sybase-indexes-t317.htm</link>
			<dc:creator>bi_at_nj</dc:creator>
			<description><![CDATA[Is yours a Sybase shop? Please specify what kind of indexing strategy you follow in your sybase databse for bi / dw applications .
<br />

<br />
What kind of indexes do u use in your warehouse / bi applications in Sybase shop? 
<br />
Do you follow any indexing strategy in Sybase?
<br />

<br />
Thanks in advance,
<br />
nj_at_bi]]></description>
			<category>Dimensional Modeling and Data Architecture</category>
			<pubDate>Sat, 31 Oct 2009 04:47:06 GMT</pubDate>
			<comments>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/sybase-indexes-t317.htm#1332</comments>
			<guid>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/sybase-indexes-t317.htm</guid>
		</item>
		<item>
			<title>Many to many relationship question</title>
			<link>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/many-to-many-relationship-question-t312.htm</link>
			<dc:creator>ekv11</dc:creator>
			<description>Hi all.  I know the common standard practice for many to many relationships is to use a bridge table, and I've done that already in my model.  But I've come across a situation where I'm thinking of using a group table related directly with the fact.  Let's use the example of an insurance policy for a trucking company.  For each policy the company can haul multiple commodities.  These commodities are free form entered into the system, along with a percentage of the total time that particular commodity  ...</description>
			<category>Dimensional Modeling and Data Architecture</category>
			<pubDate>Tue, 27 Oct 2009 22:43:18 GMT</pubDate>
			<comments>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/many-to-many-relationship-question-t312.htm#1319</comments>
			<guid>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/many-to-many-relationship-question-t312.htm</guid>
		</item>
		<item>
			<title>many to many relationship between dimension level</title>
			<link>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/many-to-many-relationship-between-dimension-level-t311.htm</link>
			<dc:creator>GBS74</dc:creator>
			<description>I need help to design dimension model. Detail of Dimension are as following:

Dimension : Student, School

Fact : Grade



1. Class_Year

2. School

3. Area

4. City

Analysis Requirement are to drill up /down by above given hierarchy



there is :

 M:1 relationship between Area and City

 M:1 relationship between School and Area.



Issue : there is M:N relationship between Class_year and School. Every school have class year 6,7 and 8 and vice versa.



fact table consist of  ...</description>
			<category>Dimensional Modeling and Data Architecture</category>
			<pubDate>Mon, 26 Oct 2009 14:51:17 GMT</pubDate>
			<comments>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/many-to-many-relationship-between-dimension-level-t311.htm#1310</comments>
			<guid>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/many-to-many-relationship-between-dimension-level-t311.htm</guid>
		</item>
		<item>
			<title>One to many relationships</title>
			<link>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/one-to-many-relationships-t308.htm</link>
			<dc:creator>Martijn Kamerbeek</dc:creator>
			<description>Hi,



I am new to dimensional modeling, would anybody be able to guide me on a design questions? An insurance policy has multiple insureds and multiple vehicles. If I create a fact table that lists the total premium for each policy, and make insureds and vehicles the dimensions; how do I link multiple insureds and multiple vehicles to the fact table? Would I use a bridge table? What would the structure be of that table and what keys would I store in the fact table?



Thanks so much for  ...</description>
			<category>Dimensional Modeling and Data Architecture</category>
			<pubDate>Fri, 23 Oct 2009 23:59:17 GMT</pubDate>
			<comments>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/one-to-many-relationships-t308.htm#1301</comments>
			<guid>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/one-to-many-relationships-t308.htm</guid>
		</item>
		<item>
			<title>Facts with different grain from different sources but related</title>
			<link>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/facts-with-different-grain-from-different-sources-but-related-t309.htm</link>
			<dc:creator>mranjank</dc:creator>
			<description>Hi,

I have a situation which I am trying to resolve but not able to 

Technologies Using : SQL Server and Analytics Services (SSAS)



Background

I have a flat file which is from the enterprise peoplesoft system and has the followings

GL Account, Company code, total amount



The oltp system sends data into the enterprise ware house and information is processed and stored in a data mart. Here is the logical structure of the information



Company Dim

===========

Comp Key, company  ...</description>
			<category>Dimensional Modeling and Data Architecture</category>
			<pubDate>Sat, 24 Oct 2009 13:13:28 GMT</pubDate>
			<comments>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/facts-with-different-grain-from-different-sources-but-related-t309.htm#1303</comments>
			<guid>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/facts-with-different-grain-from-different-sources-but-related-t309.htm</guid>
		</item>
		<item>
			<title>Dimension as a Fact</title>
			<link>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/dimension-as-a-fact-t310.htm</link>
			<dc:creator>Irtaza Hassan</dc:creator>
			<description>Is it wise to use a Dimension as a Fact table as well?



The Scenario:



Whenever a subscription based service makes a sale a Sales Fact table records all the transactions. However each sale generates a new Subscription Code as well. I am not really sure how to handle this subscription code. I am tempted to create this as a degenerate dimension in the Sales Fact. However there are various other business processes that use the subscription code generated by the Sales process e.g. Subscription  ...</description>
			<category>Dimensional Modeling and Data Architecture</category>
			<pubDate>Mon, 26 Oct 2009 10:52:28 GMT</pubDate>
			<comments>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/dimension-as-a-fact-t310.htm#1308</comments>
			<guid>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/dimension-as-a-fact-t310.htm</guid>
		</item>
		<item>
			<title>Modelling help for multiple level facts</title>
			<link>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/modelling-help-for-multiple-level-facts-t306.htm</link>
			<dc:creator>terry_stjean</dc:creator>
			<description>We have an Expense application which has an Expense Header, Expense Details and Expense GL Transactions. 

I need some help on the design. All 3 tables contain fact and dimension data.

The issue I have is in relating the 3 fact tables.

On the Dimension side, I have created tables for Date, Customer, GL Account etc.

Do I create a Fact and Dimension table for the Expense Header and then relate the Dimension Expense Header to the Expense Details Fact.

Similarly, do I create a Fact and Dimension  ...</description>
			<category>Dimensional Modeling and Data Architecture</category>
			<pubDate>Fri, 23 Oct 2009 13:32:30 GMT</pubDate>
			<comments>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/modelling-help-for-multiple-level-facts-t306.htm#1299</comments>
			<guid>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/modelling-help-for-multiple-level-facts-t306.htm</guid>
		</item>
		<item>
			<title>Modeling a fact with multiple sources</title>
			<link>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/modeling-a-fact-with-multiple-sources-t156.htm</link>
			<dc:creator>schnedar</dc:creator>
			<description>We have a situation where multiple business processes will generate a recommendation.  A recommendation is a set of instructions, estimated costs, risk analysis, etc. for identified hazards.  Examples of various business processes that generate these recommendations are a mishap investigation, workplace evaluation, hazard identification, inspection report, and a few others.



Now, the end-user wants to slice and dice either by individual source processes or all recommendations in general.  ...</description>
			<category>Dimensional Modeling and Data Architecture</category>
			<pubDate>Fri, 29 May 2009 16:19:23 GMT</pubDate>
			<comments>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/modeling-a-fact-with-multiple-sources-t156.htm#724</comments>
			<guid>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/modeling-a-fact-with-multiple-sources-t156.htm</guid>
		</item>
		<item>
			<title>Hierarchy within single dimension or two dimensions</title>
			<link>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/hierarchy-within-single-dimension-or-two-dimensions-t305.htm</link>
			<dc:creator>jimbo1580</dc:creator>
			<description>I am unsure of the best way to model a specific business scenario and was looking for some input.  I will explain it in terms of a common example, the Product dimension.  Let's say that every &quot;product&quot; is assigned to a specific &quot;department&quot;.  How would you model this relationship if department has a few other attributes besides &quot;name&quot; that we are also interested in, such as department number, department size, and department manager?  In this case &quot;department&quot;  ...</description>
			<category>Dimensional Modeling and Data Architecture</category>
			<pubDate>Wed, 21 Oct 2009 18:46:22 GMT</pubDate>
			<comments>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/hierarchy-within-single-dimension-or-two-dimensions-t305.htm#1286</comments>
			<guid>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/hierarchy-within-single-dimension-or-two-dimensions-t305.htm</guid>
		</item>
		<item>
			<title>Pipeline with Accumulating snapshot</title>
			<link>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/pipeline-with-accumulating-snapshot-t302.htm</link>
			<dc:creator>sr_da</dc:creator>
			<description>I have accumulating snapshot design for insurance new business workflow process. The current grain in the fact table is policy level with all associated dates and measures from policy submission to being issued. So, in summary I have one activce entry per policy in the fact table. This is working very well in current BI environment.



Need help on the following new requirement: 

Policy dimension can have many underwriting requirements associated to it. Similarly policy dimension is associated  ...</description>
			<category>Dimensional Modeling and Data Architecture</category>
			<pubDate>Tue, 20 Oct 2009 03:06:44 GMT</pubDate>
			<comments>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/pipeline-with-accumulating-snapshot-t302.htm#1275</comments>
			<guid>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/pipeline-with-accumulating-snapshot-t302.htm</guid>
		</item>
		<item>
			<title>Combining Facts</title>
			<link>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/combining-facts-t304.htm</link>
			<dc:creator>cbusch</dc:creator>
			<description>We have 2 entities in our logical model for authorizations.  One for inpatient authorizations and another for service authorizations.  They are both children of the parent authorization entity.



We are considering combining them into a single authoriztion fact in our dimensional model.  The table would be an accumulating snapshot updated daily.  There are about 100 attributes of which 25 are specific to inpatient and 25 are specific to services.  The total volume is &lt; 1 million.



The  ...</description>
			<category>Dimensional Modeling and Data Architecture</category>
			<pubDate>Tue, 20 Oct 2009 19:09:45 GMT</pubDate>
			<comments>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/combining-facts-t304.htm#1278</comments>
			<guid>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/combining-facts-t304.htm</guid>
		</item>
		<item>
			<title>Data Warehouse Purge Strategy - HELP</title>
			<link>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/data-warehouse-purge-strategy-help-t300.htm</link>
			<dc:creator>AndyPainter</dc:creator>
			<description>I'm looking at the best way to implement a purge strategy in a dimensional model.  The reason to purge is that no personal data can be kept after 4 years, but the users would still want to see counts/facts by no identifying data.  For example i couldn't keep a name, but i could keep the gender or employer.



Is it best to do this by depersonalising data e.g. setting certain column to NULL after a number of years, or adopting an aggregate strategy.  The data volumes are not huge, but if i go  ...</description>
			<category>Dimensional Modeling and Data Architecture</category>
			<pubDate>Mon, 19 Oct 2009 19:54:12 GMT</pubDate>
			<comments>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/data-warehouse-purge-strategy-help-t300.htm#1268</comments>
			<guid>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/data-warehouse-purge-strategy-help-t300.htm</guid>
		</item>
		<item>
			<title>Subscription as an Accumulating Snapshot Fact or a Dimension?</title>
			<link>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/subscription-as-an-accumulating-snapshot-fact-or-a-dimension-t299.htm</link>
			<dc:creator>Irtaza Hassan</dc:creator>
			<description>I am designing a data mart for a subscription based service (my first data modelling effort). Each customer can have multiple accounts and each account can have multiple subscriptions.  I have added a Sales Fact table and a Monthly Subscription Snaphot Fact table.



However I am confused about handling of subscriptions. We need to keep track of Registration date, Activation date and Cancellation date to determine the status of each subscription. We also need to track the Training Booking,  ...</description>
			<category>Dimensional Modeling and Data Architecture</category>
			<pubDate>Mon, 19 Oct 2009 09:31:36 GMT</pubDate>
			<comments>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/subscription-as-an-accumulating-snapshot-fact-or-a-dimension-t299.htm#1263</comments>
			<guid>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/subscription-as-an-accumulating-snapshot-fact-or-a-dimension-t299.htm</guid>
		</item>
		<item>
			<title>Millions of client information that can not be uniquely identified</title>
			<link>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/millions-of-client-information-that-can-not-be-uniquely-identified-t298.htm</link>
			<dc:creator>hennie7863</dc:creator>
			<description>Hi



Every client of an organization at which i'm employed can not be uniquely identified. In this organization 30 milions of clients per year are registered. From every client a birthname, adres, birthdate, etc is registered. In theory it's possible that double customers occur (and possibly not the same).



In my proposal i suggested that for every registration a customer is inserted into a customer dimension. So for every fact record a dimensionrecord is inserted. Of course analysis is  ...</description>
			<category>Dimensional Modeling and Data Architecture</category>
			<pubDate>Mon, 19 Oct 2009 07:14:30 GMT</pubDate>
			<comments>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/millions-of-client-information-that-can-not-be-uniquely-identified-t298.htm#1262</comments>
			<guid>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/millions-of-client-information-that-can-not-be-uniquely-identified-t298.htm</guid>
		</item>
		<item>
			<title>Start schema in relational database vs OLAP</title>
			<link>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/start-schema-in-relational-database-vs-olap-t269.htm</link>
			<dc:creator>dellsters</dc:creator>
			<description>I understand what OLAP and MOLAP are and their purpose in theory. Under what scenarios would one consider switching from start schemas in relational database to OLAP technology and building cubes? I understand this is more frequent in financial departments. Can one expand more about the usage? I understand it improves performance, but you can get pretty good performance by having star schemas in relational databses right? 



And to move to OLAP technology, can you elaborate how it would be?  ...</description>
			<category>Dimensional Modeling and Data Architecture</category>
			<pubDate>Thu, 10 Sep 2009 01:37:20 GMT</pubDate>
			<comments>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/start-schema-in-relational-database-vs-olap-t269.htm#1147</comments>
			<guid>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/start-schema-in-relational-database-vs-olap-t269.htm</guid>
		</item>
		<item>
			<title>Best Practices for SCD Dimension Tables for a Banking Data Warehouse</title>
			<link>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/best-practices-for-scd-dimension-tables-for-a-banking-data-warehouse-t292.htm</link>
			<dc:creator>IJohnson</dc:creator>
			<description><![CDATA[Hello,
<br />

<br />
I am looking for a list of dimension tables to track historical changes on for a banking data warehouse, based on &quot;best practices&quot;.  Customer is a prime candidate.  Are there others?  
<br />

<br />
Thanks,
<br />

<br />
Ike]]></description>
			<category>Dimensional Modeling and Data Architecture</category>
			<pubDate>Wed, 14 Oct 2009 19:36:03 GMT</pubDate>
			<comments>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/best-practices-for-scd-dimension-tables-for-a-banking-data-warehouse-t292.htm#1250</comments>
			<guid>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/best-practices-for-scd-dimension-tables-for-a-banking-data-warehouse-t292.htm</guid>
		</item>
		<item>
			<title>Measures as special dimension table</title>
			<link>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/measures-as-special-dimension-table-t297.htm</link>
			<dc:creator>Kraft</dc:creator>
			<description><![CDATA[I am modeing a data warehouse for a manufacturing industry. The issue I had is there are too many measures for one particular business process. Say for a work centre, we have 20 measures, and each measure might have different unit of measures. Is is a good idea to create a dimension table say DimMeasures to hold these measures instead of creating many columns in facts table? 
<br />

<br />
Thanks!]]></description>
			<category>Dimensional Modeling and Data Architecture</category>
			<pubDate>Fri, 16 Oct 2009 19:03:27 GMT</pubDate>
			<comments>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/measures-as-special-dimension-table-t297.htm#1258</comments>
			<guid>http://kimballgroup.forumotion.net/dimensional-modeling-and-data-architecture-f6/measures-as-special-dimension-table-t297.htm</guid>
		</item>
	</channel>
</rss>