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?

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...