Like I said earlier to your core question... "Yes". 

It's just a bad idea to shrink files that are destined to grow again because of file fragmentation.  You must first...

No problem, Noel... it's easy to see how I might have been taken because I was pretty adamant about the whole IDENTITY thing.

So,...

Eamon,

I was a bit out of line... I should have asked why you need to do this so we can come up with the best solution for your circumstance. 

So,...

So... someone wanna ask the OP what's up?

You can protect your database if you create it as a separate instance of SQL Server and make "linked servers" for the client to yours... of course, linked servers create...

Sorry... not familiar with either the tool or the product, Lakshmi.

Can anyone else help Lakshmi?

Does it support the following query?

 SELECT * FROM SysIndexes

In that case, the answer to your original question is "YES".

I suppose I shouldn't mention it because it is outside the original question, but shrinking the file and having it...

None... we don't use replication for replication

Anyway, wasn't meant to be a challenge, Noel... was just curious.

If it's mission critical as you say, why not just buy some more harddisk space?  That's a lot cheaper than losing data...

Just curious, Noeld... how many databases have you built with a Sequence table of this nature?

The SET statement does not allow the following...

SET #TempRecordsToCreate.ShortName = CODE_PROGRAM.CODE_VALUE

Remove the code in red and it should work fine...

Thanks, Sugesh...

I think we scared the OP away...

>>but it executes faster than your user cursor

Who's "user cursor" solution are you talking about, Sugesh?