Re: Exhaused sequence
- From: Tim Gorman <tim@xxxxxxxxx>
- To: "'Oracle-L@xxxxxxxxxxxxx'" <Oracle-L@xxxxxxxxxxxxx>
- Date: Thu, 17 Feb 2005 21:00:13 -0700
Sequences were invented specifically to resolve problems in block contention
(i.e. "buffer busy waits") resulting from this method of doling out keys.
And who knows how long the application's transactions exist -- this table of
numbers can become a bottleneck quite easily, if the concurrency gets high
enough...
on 2/17/05 7:50 PM, Thomas Day at tomday2@xxxxxxxxx wrote:
> During off hours create a table that has all the missing numbers from
> your column. Select your new customer number by selecting
> min(missing_number) from that table and then have an after insert
> trigger that deletes the min(missing_number). When your new table has
> 0 rows you're done.
>
> It'll get rid of the slow inserts from real-time searching for
> available numbers but your customer should re-think their business
> rule. Unless they plan on limiting their growth they need to expand
> the column.
> --
> //www.freelists.org/webpage/oracle-l
>
--
//www.freelists.org/webpage/oracle-l
Other related posts:
