CREATE TABLE [dbo].[Component](
	[ComponentID] [int] NOT NULL,
	[ComponentDescription] [varchar](50) COLLATE Latin1_General_CI_AS NOT NULL,
	[ParentComponentID] [int]  NULL,
 CONSTRAINT [PK_Component] PRIMARY KEY CLUSTERED 
(
	[ComponentID] ASC
))

ALTER TABLE [dbo].[Component]  WITH CHECK ADD  CONSTRAINT [FK_Components_ComponentID] FOREIGN KEY([ParentComponentID])
REFERENCES [dbo].[Component] ([ComponentID])


INSERT INTO component SELECT 1, 'Biggest Widget', NULL
INSERT INTO component SELECT 2, 'Big Widget A', 1
INSERT INTO component SELECT 3, 'Big Widget B', 1
INSERT INTO component SELECT 4, 'Widget C', 3
INSERT INTO component SELECT 5, 'Widget D', 3
INSERT INTO component SELECT 6, 'Widget E', 2
INSERT INTO component SELECT 7, 'Small Widget G', 5
INSERT INTO component SELECT 8, 'Small Widget H', 5

quote:

---

Originally posted by LoztInSpace

One thing I would suggest is to separate your data model from your user interface. Starting to think of a database design around a tree view is dangerous - you need to consider all your business requirements first. Do you have more than one parent for each component for example, would you need to generate a pick list? etc. etc.
Separate the two and you'll find yourself writing much better products.

---