Hi,
I am using a table of single row for next number,
Table Name - SequenceOID
column name - NextOID varchar(32)
this nextOID number is used for PK of system wide tables. Thru a stored procedure(GetNextOID) i am taking the currect value of that single row column NextOID and table SequenceOID is updated by next number.
Locking problem starts when in same Transaction multiple processes call for the next number from table sequenceOID .To solve this problems i need a autonomous transactions like feature (in oracle db), i.e. calling of procedure for next number from that table must be a independept (autonomous transaction) transaction so that it will commit immediately irrespective of Parent transactions transaction state wether it will finally commit or rollback.
I will be grateful if anybody can help me urgently.
Thanks,
Shailesh
I am using a table of single row for next number,
Table Name - SequenceOID
column name - NextOID varchar(32)
this nextOID number is used for PK of system wide tables. Thru a stored procedure(GetNextOID) i am taking the currect value of that single row column NextOID and table SequenceOID is updated by next number.
Locking problem starts when in same Transaction multiple processes call for the next number from table sequenceOID .To solve this problems i need a autonomous transactions like feature (in oracle db), i.e. calling of procedure for next number from that table must be a independept (autonomous transaction) transaction so that it will commit immediately irrespective of Parent transactions transaction state wether it will finally commit or rollback.
I will be grateful if anybody can help me urgently.
Thanks,
Shailesh