>Ideally I would prefer not to use my own key generator because I will need to make adjustments to my connected app that uses "Select @@Identity" to get the key back. Would my custom generator be able to set the @@identity value so my app would not need to change?
You can create a separate table with one column of IDENTITY type and use it as key generator. This way @@Identity will return the last identity assigned. But it's more like kludge from my POV.
>Assuming I cannot force MS SQL to not update the next seed value when I do an identity insert or just always use the next lowest value available (either of which would solve the problem), any ideas where would be a good place to look for a good integer key generator for MS SQL 2000?
>
Check
Next Number generator Message #
534192
--sb--