Don't you determine entities and relationships first, and then determine groupings of those and put those into schemas?

Your questions are REALLY vague. Maybe you should clarify them.

Okay, here's my screenshot. It's starting to make more sense. If I move up the hierarchy from a leaf node to the root, I just multiply the quantity at each...

Jeff,

(and Steve, who's kinda busy this week) and anybody else... for grins, I did a PPT of this so I could see the hierarchy and understand what's going on "in...

Jeff,

Gotta get some sleep... Just got home, so I'll do it in the morning sometime. It's a really simple tree with 3 levels, but I think it's enough to get...

Just to explain it to myself or visualize what's going on, I drew a tree of parts with assemblies etc. I started with something I could get my head around...

Something like this? (Use a Calendar table).

use tempdb;
GO
-- count the dates between two days excluding weekends
CREATE TABLE #Calendar (TheDate DATE PRIMARY KEY CLUSTERED);
GO
DECLARE @TheDate  DATE = '01-Jan-2019'
WHILE...

Got some dummy data? Create table script... you know the drill.

That’s what I was thinking. Get max of level and return all parts having that same level.

Makes sense! Thanks!

This worked... ugly, but it worked:

DECLARE @string VARCHAR(200) = 'All I want (for Christmas) is better (TSQL) coding skills (this year).'
--remove everything between parens
--remove the parens
DECLARE @StartPos...

Use CHARINDEX() to find the position of the open/close parens, and then use SUBSTRING() to get the parts between them, and REPLACE() to swap that with an empty string?

Sounds like...

Aaron,

is there an easy way to identify those?

Pieter

Live and learn, I guess.

I might have to revisit this and rewrite it when I learn how to do it better. I think part of the challenge is that it's...

The part I finally figured out that threw me at first is that you filter what the CTE returns by adding a WHERE clause outside the CTE (seems to painfully...

FWIW, here's my current code... I *think* it works, but maybe it's just AdventureWorks playing tricks on me.

CREATE PROC PartsSheetForSalesOrder
 @SalesOrderID INT
AS
WITH Parts(AssemblyID, ComponentID, PerAssemblyQty, EndDate, ComponentLevel) AS ...

Here's my code so far... How do I just return the lowest level components? I feel like I'm missing a join or something somewhere...

Here's my code so...