Yep... then make sure that you rename the column in every stored procedure, view, UDF, foreign key, etc, that uses that column in all databases...

What have you tried? 

Now, THAT's what I'm talkin' 'bout

Might also find it useful to put your "Numbers" or "Tally" table there along with an auxiliary date table... make sure you keep the code to build them safe for when...

Micheal Valentine Jones has a faster way but this is an easy way...

Step 1.  Create a permanent Tally table... (it has many, many uses)

--===== Create and populate the...

Heh.... agreed... poor ol' Adam already admitted that the whacko that designed this headed for the hills a long time ago... Who would do this?  I can (possibly) understand needing...

That's a great suggestion... guaranteed to not duplicate between tables and no trigger overhead.

That's a cool function... change the 36 to 27 and drop the 1-9 from the string and I think it'll work for the 0, A-Z range...

Like I said, keep the identity column and add a calculated column.  Takes care of new rows, old rows, etc...   Or, you...

Heh... speak of the devil and who shows up?  I just recommended your sequential numbers function... was writin' while you were postin'

Hey there Harley,

Thanks for the compliment...  You and Paul made my day!

Sadly, in SQL Server 2000, there's no way to return the equivelent of row numbers using a SELECT without using...

I do not think there is a way where you can use Update to update based on counter

I...

Hey Paul,

I almost forgot a trick with using this if you can't make a "sister table".... you can force the order by using an index hint... like this... (this is...

Heh... thanks, Paul... I always wonder if anyone reads these things...

Just so you know I'm not using some whacko, back door, undocumented construct,...