I've hit a bit of a mental block on my database design
essentially it's a tree view of a company's assets - so naturally hierarchyid is the natural candidate for this...
effectively it's one table with a hierarchy id as the natural key (maybe an artificial key to make things a bit easier) - think of it a bit like a windows folder structure but each node in the tree is a different "node type"
My dilemma is - we have multiple customers using this structure, so do I incorporate them into the node design , or do I make a foreign key to a customers table and have each node in the tree FK'd off to the company?
I suppose I'm asking do I have a forest or lots of little trees with unnecessary labels on each leaf?