On Wed, Mar 25, 2009 at 9:39 PM, Niall Litchfield < niall.litchfield@xxxxxxxxx> wrote: > Hi Greg > > fm > > for gapless, you have to consider what you want to happen when a thread > grabs a block of numbers and doesn't use them all (dies,bug, server restart > etc etc). you also *have* to serialize access to the current value of the > counter. gapless sequences will kill scalability (or actually not be > gapless). As Jared suggested it's well worth investigating what the business > requirement actually is, and if it can be met in some other way. Usually > it's a misstated audit requirement. > > Gints has a good discussion at http://www.gplivna.eu/papers/gapless_sequences.htm as well. -- Niall Litchfield Oracle DBA http://www.orawin.info