Works fine (pretty cool solution, too, Peter) if you guarantee the order by loading a temp table... bit of a problem otherwise...

-- Prepare sample data

DECLARE    @Sample TABLE (RowID INT IDENTITY(1,1), col1...

Thanks for posting what you've found, Elliott 

You want just the names of the PK's and FK's along with the related table name?

Have you considered just using TSQL and a call to OSQL?

In light of Peter's solution, I'd have to say "Yeah, you're wrong"   Also, what's wrong with putting "the work in the query"?  Isn't...

God forbid you do any real advertising

Don't forget... Op wants numbers to restart at 1 at the beginning of each group.

Read the post, Joe... he's a rookie and he said he'd take the advice I gave him to format in the front end

Heh... or concatenate the groups on a single line?

Heh... that's why I asked to see the code... I'll be doing the ol' million row testing on these solutions tonight... Ladies and Gentlemen, place your bets

Or... just use the set based solution I provided to do the whole table at once

Using John's good test setup... this is 1 place where a triangular join may work well because the groups indicated by Col1 are so small...

DECLARE @Table TABLE (RowID int IDENTITY(1,1),...

BTW... couldn't help but notice you're using @@IDENTITY... if a trigger is present, that could mess things up because @@IDENTITY returns the last id of ANY table updated.  Recommend you...

You bet, Adam.  Thanks for posting back.