Heh... appreciate that, David... now, all I have to do is convince Eamon as to what a terrible mistake using that type of sequence table is

There might be something else going on, but can't tell unless you post the sproc

Step 1.  Nominate the current DBA for a "Darwin Award".

Step 2.  Fire the current DBA.

Step 3.  Promote the developer to DBA with the caveat that if he doesn't impliment the...

>>is there a reason you can't do an insert into the sequence table and store scope_identity into a variable

Yes... the sequence table only has one row according to the OP... so...

Correct... in a properly designed database, the assemblies and sub-assemblies would not only be separated, but they would be "normalized" as well.  Separate table would also be present to identify...

That's why I'm saying you've gotta normalize it... you can submit the answers to the questions all at the same time, just not all in one row.  Your current design...

I guess I should explain the other reasons why this is gonna "suck" and why I don't think this resembles a relational database... you're using RBAR (pronounced "ree-bar" and is...

Heh... we had something similar that a 3rd party built into their part of our database... 640 average deadlocks per day with spikes to 4,000

Even though SQL Server 2000 doesn't have a pivot function, it's pretty darned easy to make one.  So, don't let the lack of a pivot function make you do something...

Heh... it wouldn't be just me that gets annoyed... some folks get downright rude about cross posting.

Anyway, glad to help and thanks for the feedback.

Thanks for the example of what this type of sort might be used by... brought back some memories of how the Navy designates assemblies and sub-assemblies (A4A1A13CR5).  Also, might need...

CROSS POST... see the following

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=338&messageid=376138&post=true

First, it really ticks folks off when you double post like you did... this is one place where you do need to put all your eggs in one basket... keeps...

A bit late with a response... but you do understand that temp tables are automatically dropped when the session that created it ends?

Just to add to the above... In SQL Server 7.0...

If neither Item 4 or 8 are set, that's the equivelent to FULL recovery.

IF Item 4 is set and Item 8...