[DUG] MSSQL Question

[Kyley Harris]

pretend IDENTITY columns dont exist, because they don't do what I want,
which is to create non-rollback numbers like IB Generators or Oracle
Sequences.
No matter how much rowlocking, updatelocks etc.. if a rollback happens then
the Sequence numbers can get scrambled depending on transaction order.

I've read under SQL 2008 (im using '05) that you can create a remote stored
procedure using a loobback connection, where the remote call will then
commit the increments outside of the local transaction running? Can anyone
confirm this?

My only other thought is to write a CLR (when I learn how) that uses
critical sections and a seperate database connection to access and do all
the commits to the Sequence generation table..

any thoughts comments appreciated.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://listserver.123.net.nz/pipermail/delphi/attachments/20081201/77571f63/attachment.html