No, for various reasons. You mentioned load, and that's an issue, then there's the concurrency problem, and the fact that a 'roll your own sequence number generator' usually relies on the current MAX() of the column in question which cannot be determined when uncommitted inserts are in play. I talked about some of this a good while back: http://dfitzjarrell.wordpress.com/2008/06/06/out-of-sequence/ It's still a pretty good read, though. :) David Fitzjarrell ________________________________ From: Johan Eriksson <valpis@xxxxxxxxx> To: Oracle Discussion List <oracle-l@xxxxxxxxxxxxx> Sent: Friday, April 12, 2013 9:24 AM Subject: Stupidity or sequences? Hi all, I think most of us has seen someone trying to be smart or trying to gain database independencies by not using oracle sequence but instead roll their own system by using a table, and a row for each "sequence". Almost every attempt on this I yet have seen has been plagued with row lock contention or other concurrencies, scalability zero... Have anyone actually seen some implementation of this kind work when load increase? /johan -- //www.freelists.org/webpage/oracle-l -- //www.freelists.org/webpage/oracle-l