<?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: Handling Recursive Hierarchies in SQL Server</title>
	<atom:link href="http://www.bimonkey.com/2009/09/handling-recursive-hierarchies-in-sql-server/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bimonkey.com/2009/09/handling-recursive-hierarchies-in-sql-server/</link>
	<description>James Beresford on Microsoft BI and Consulting in Sydney, Australia</description>
	<lastBuildDate>Mon, 06 Feb 2012 16:00:48 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: BI Monkey</title>
		<link>http://www.bimonkey.com/2009/09/handling-recursive-hierarchies-in-sql-server/comment-page-1/#comment-13081</link>
		<dc:creator>BI Monkey</dc:creator>
		<pubDate>Thu, 20 Oct 2011 01:05:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.bimonkey.com/?p=596#comment-13081</guid>
		<description>Sorry Gary, I rarely touch Oracle so don&#039;t have a translated version available.</description>
		<content:encoded><![CDATA[<p>Sorry Gary, I rarely touch Oracle so don&#8217;t have a translated version available.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gary</title>
		<link>http://www.bimonkey.com/2009/09/handling-recursive-hierarchies-in-sql-server/comment-page-1/#comment-12856</link>
		<dc:creator>Gary</dc:creator>
		<pubDate>Wed, 12 Oct 2011 12:20:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.bimonkey.com/?p=596#comment-12856</guid>
		<description>I am using the Kimball Helper Table Method perfectly against a SQL-Server database.  The only problem is I am now having to port to and Oracle 10(something) database.

The code does not work in this environment, so I wondered if you had Oracle equivalent code available?

If yes I would greatly appreciate a copy.</description>
		<content:encoded><![CDATA[<p>I am using the Kimball Helper Table Method perfectly against a SQL-Server database.  The only problem is I am now having to port to and Oracle 10(something) database.</p>
<p>The code does not work in this environment, so I wondered if you had Oracle equivalent code available?</p>
<p>If yes I would greatly appreciate a copy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike</title>
		<link>http://www.bimonkey.com/2009/09/handling-recursive-hierarchies-in-sql-server/comment-page-1/#comment-6007</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Thu, 17 Mar 2011 19:48:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.bimonkey.com/?p=596#comment-6007</guid>
		<description>The problem with the LR Method, otherwise known as Nested Sets, is inserting, deleting and moving nodes to other parents. When you do one of these things, you have to update all the left and right nodes to compensate for the change. If you&#039;ve put indexes on your Left and Right columns (to improve query performance) and you update a node in a tree with hundreds of thousands of records, you may need to write tens of thousands of updates to left and right columns when you change just one node.

So, Nested Sets may be good for a content publishing system where updates don&#039;t need to happen in real time, but it&#039;s not ideal for an active web application, especially a distributed one, where reaction time is important.</description>
		<content:encoded><![CDATA[<p>The problem with the LR Method, otherwise known as Nested Sets, is inserting, deleting and moving nodes to other parents. When you do one of these things, you have to update all the left and right nodes to compensate for the change. If you&#8217;ve put indexes on your Left and Right columns (to improve query performance) and you update a node in a tree with hundreds of thousands of records, you may need to write tens of thousands of updates to left and right columns when you change just one node.</p>
<p>So, Nested Sets may be good for a content publishing system where updates don&#8217;t need to happen in real time, but it&#8217;s not ideal for an active web application, especially a distributed one, where reaction time is important.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brett</title>
		<link>http://www.bimonkey.com/2009/09/handling-recursive-hierarchies-in-sql-server/comment-page-1/#comment-2897</link>
		<dc:creator>Brett</dc:creator>
		<pubDate>Fri, 05 Nov 2010 16:03:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.bimonkey.com/?p=596#comment-2897</guid>
		<description>Your solution helped me tremendously! I was trying to avoid some large recursive queries. Thanks!!!</description>
		<content:encoded><![CDATA[<p>Your solution helped me tremendously! I was trying to avoid some large recursive queries. Thanks!!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brenda Brink</title>
		<link>http://www.bimonkey.com/2009/09/handling-recursive-hierarchies-in-sql-server/comment-page-1/#comment-1859</link>
		<dc:creator>Brenda Brink</dc:creator>
		<pubDate>Wed, 26 May 2010 13:54:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.bimonkey.com/?p=596#comment-1859</guid>
		<description>I don&#039;t understand Fig. 7 in your example.  Kimball&#039;s article says that the depth from parent  counts how many levels the subsidiary is below the parent.  For example, it seems that DFP for A1-A4 should be 2, not 1, and for A6-A6 should be 0, not 2.  What am I missing?</description>
		<content:encoded><![CDATA[<p>I don&#8217;t understand Fig. 7 in your example.  Kimball&#8217;s article says that the depth from parent  counts how many levels the subsidiary is below the parent.  For example, it seems that DFP for A1-A4 should be 2, not 1, and for A6-A6 should be 0, not 2.  What am I missing?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BI Monkey</title>
		<link>http://www.bimonkey.com/2009/09/handling-recursive-hierarchies-in-sql-server/comment-page-1/#comment-1657</link>
		<dc:creator>BI Monkey</dc:creator>
		<pubDate>Wed, 28 Apr 2010 20:24:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.bimonkey.com/?p=596#comment-1657</guid>
		<description>The scripts here aren&#039;t able to cope with that. From a dimensional perspective it then becomes a design decision about how you handle such cases. Can you support multiple hierarchies for example? Or set up a scenario where data is duplicated to handle each parent? Not easy!</description>
		<content:encoded><![CDATA[<p>The scripts here aren&#8217;t able to cope with that. From a dimensional perspective it then becomes a design decision about how you handle such cases. Can you support multiple hierarchies for example? Or set up a scenario where data is duplicated to handle each parent? Not easy!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: la</title>
		<link>http://www.bimonkey.com/2009/09/handling-recursive-hierarchies-in-sql-server/comment-page-1/#comment-1656</link>
		<dc:creator>la</dc:creator>
		<pubDate>Wed, 28 Apr 2010 13:27:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.bimonkey.com/?p=596#comment-1656</guid>
		<description>what happens to the sum when a node has multiple parent ?</description>
		<content:encoded><![CDATA[<p>what happens to the sum when a node has multiple parent ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BI Monkey</title>
		<link>http://www.bimonkey.com/2009/09/handling-recursive-hierarchies-in-sql-server/comment-page-1/#comment-1614</link>
		<dc:creator>BI Monkey</dc:creator>
		<pubDate>Sun, 18 Apr 2010 07:28:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.bimonkey.com/?p=596#comment-1614</guid>
		<description>As in the example, just use Count instead of Sum - too easy :)</description>
		<content:encoded><![CDATA[<p>As in the example, just use Count instead of Sum &#8211; too easy <img src='http://www.bimonkey.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SRB1</title>
		<link>http://www.bimonkey.com/2009/09/handling-recursive-hierarchies-in-sql-server/comment-page-1/#comment-1612</link>
		<dc:creator>SRB1</dc:creator>
		<pubDate>Sat, 17 Apr 2010 16:51:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.bimonkey.com/?p=596#comment-1612</guid>
		<description>Please, show ho to get the number of children for each parent.</description>
		<content:encoded><![CDATA[<p>Please, show ho to get the number of children for each parent.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BI Monkey</title>
		<link>http://www.bimonkey.com/2009/09/handling-recursive-hierarchies-in-sql-server/comment-page-1/#comment-1381</link>
		<dc:creator>BI Monkey</dc:creator>
		<pubDate>Wed, 24 Feb 2010 00:41:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.bimonkey.com/?p=596#comment-1381</guid>
		<description>RHD110, i&#039;m not 100% sure I follow but this is my understanding:

1) Each &lt;strong&gt;assembly &lt;/strong&gt;can have a sub-&lt;strong&gt;assembly&lt;/strong&gt;
2) Each &lt;strong&gt;assembly &lt;/strong&gt;can have multiple items

The issue you have is that because each assembly can have multiple items you cannot simply express the items as a property of the assembly.

I can see a couple of options for the display of this, depending on what suits your business needs:

1) Have an Assembly hierachy which is separate from your item dimension &lt;em&gt;or&lt;/em&gt;
2) Treat each Assemblys items as part of the Assembly hierarchy, and indicate that an Item is not strictly part of the assembly hierarchy (e.g. with a prefix on the member name)

Cheers, James</description>
		<content:encoded><![CDATA[<p>RHD110, i&#8217;m not 100% sure I follow but this is my understanding:</p>
<p>1) Each <strong>assembly </strong>can have a sub-<strong>assembly</strong><br />
2) Each <strong>assembly </strong>can have multiple items</p>
<p>The issue you have is that because each assembly can have multiple items you cannot simply express the items as a property of the assembly.</p>
<p>I can see a couple of options for the display of this, depending on what suits your business needs:</p>
<p>1) Have an Assembly hierachy which is separate from your item dimension <em>or</em><br />
2) Treat each Assemblys items as part of the Assembly hierarchy, and indicate that an Item is not strictly part of the assembly hierarchy (e.g. with a prefix on the member name)</p>
<p>Cheers, James</p>
]]></content:encoded>
	</item>
</channel>
</rss>

