<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: Not Your Kimball&#8217;s DW	</title>
	<atom:link href="https://prologika.com/not-your-kimballs-dw/feed/" rel="self" type="application/rss+xml" />
	<link>https://prologika.com/not-your-kimballs-dw/</link>
	<description>Business Intelligence Consulting and Training in Atlanta</description>
	<lastBuildDate>Sun, 14 Aug 2022 09:41:06 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.3</generator>
	<item>
		<title>
		By: Michael Mertens		</title>
		<link>https://prologika.com/not-your-kimballs-dw/#comment-836</link>

		<dc:creator><![CDATA[Michael Mertens]]></dc:creator>
		<pubDate>Sun, 14 Aug 2022 09:41:06 +0000</pubDate>
		<guid isPermaLink="false">https://prologika.com/?p=8582#comment-836</guid>

					<description><![CDATA[Thank you for this article. I agree totally, and you don&#039;t even need an extreme example with 4.500 fields to encounter these characteristics. Just a standard extractor table from SAP CO ledger has more than 100 fields, and is an example for these thoughts. Indeed we have the distinction into &quot;important&quot; dimensions with hierarchies and so on (and there we use surrogate keys), typically shared with other fact tables, then &quot;small&quot; dimensions built by select distinct, and just pure attributes that are just staying in the fact tables &quot;as they are&quot;.]]></description>
			<content:encoded><![CDATA[<p>Thank you for this article. I agree totally, and you don&#8217;t even need an extreme example with 4.500 fields to encounter these characteristics. Just a standard extractor table from SAP CO ledger has more than 100 fields, and is an example for these thoughts. Indeed we have the distinction into &#8220;important&#8221; dimensions with hierarchies and so on (and there we use surrogate keys), typically shared with other fact tables, then &#8220;small&#8221; dimensions built by select distinct, and just pure attributes that are just staying in the fact tables &#8220;as they are&#8221;.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
