OpenEdge native sequences ca now be mapped directly to native sequences in MS SQL Server. This mapping alternative eliminates contention-related issues during ABL sequence operations. When using native sequences in your OpenEdge sequencemapping, sequence numbers are assigned independent of the application's transaction and this ensures that there is no contention. The performance is improved as there is no locking and sequence caching is possible with the use of Native Sequence generator. It simplifies the support infrastructure required for sequence generation and the sequence equation.
The following are improved with the introduction of the Native Sequence generator:
Sequence value acquisition performance
record creation performance
Note: While using DataServer for MS SQL server, if a user sets the current value of a native sequence, the start value is modified with the value provided in the SET CURRENT VALUE statement. If the NEXT-VALUE is called in a repeated loop till it reaches the maximum value of the sequence with the Cycle option active, the NEXT-VALUE restarts from the native sequence start value that is set by the last SETCURRENT-VALUE operation. It does not restart from the start value when the sequence was created. If the SET CURRENT-VALUEis not called, the NEXT-VALUE restarts with the start value that is set when the sequence is created.
Sequence value acquisition performance