Re: Thousands of sequences OK?

Doesn't seem to be a very good idea - as others have pointed out, each sequence is an object in the dc_rowcache. On the other hand, does each user have 90 table of their own ? If so the sequence thing is a less significant
part of you problems.

However, if you really need to give each user their own sequence for each table, you might as well give each user a 'sequence rows' in a sequence table.

e.g

    seq_thing1 is a table of 10,000 rows (approx) for base table thing1     user 99 increments on the row in seq_thing1 where id=99.

Jonathan Lewis
Yet another Oracle-related web site: www.jlcomp.demon.co.uk

Jerry Brennock wrote in message <36A52DA4.94FE7116_at_icat.com>...
>
>I have an application that is being migrated onto Oracle. It uses a
>table to generate unique ids, with all the associated performance and
>locking problems.
>
>The problem is that the app has been modified to give each primary user
>(web user, not actual oracle user entity) his/her own ids.
>
>I would like to replace the id table with sequences, but I could end up
>with roughly 10,000 people X 90 tables = 900,000 sequences. (There are
>also some options to get this down to about 40,000) My guess is that
>this would be politely referred to as a bad idea, but I would like to
>find out if anyone has created thousands of sequences in a database and
>what the result was. Or, if anyone knows some theoretical reason this
>would be bad.
>
>Thanks,
>
>Jerry
Received on Wed Jan 20 1999 - 14:25:34 CST