SQL Server, and ANSI SQL in general, do not make hierarchical data operations easy. The primary reason, IMO, is that hierarchical traversals are basically a row-oriented operation, which is counter to SQL's set-based approach.

There are some work-arounds though. I presented a session on Tree manipulation in SQL Server at this years DevTeach conference. I've mailed the paper to you.

HTH

-Mike

>Can someone show how to setup table(s) to make querying hierarchical data easier and perhaps share a simple SQL to query it?
>
>For example, if I wanted to setup and lstore family geneology info. then later query "all" descendants of a particular person within the tree how would I go about doing this? TIA.