Re: One SEQUENCE, many tables .. need advice

Thanks, Dan and Ian. I think I'll go with the single sequence then..it just keeps things simpler.

Anne

Ian Ledzion wrote:

> Thought both approaches are equally valid, I'd go for the single sequence
> option on the basis that you then have a Unique Object Identifier in you
> database.
>
> "Anne Nolan" <anolan_at_enabletech.com> wrote in message
> news:3B42325E.3A7DCAD8_at_enabletech.com...
> > Hi all,
> >
> > I'm working on designing a whole new database. I've decided to go with
> > surrogate keys generated from sequences for most of the primary keys in
> > the tables.
> >
> > Is it OK or even advisable to use one sequence for generating all these
> > keys? Or should each table have its own sequence for generating its
> > keys? I presume there is no ultimate upper limit to how big a
> > sequence value can get..is this true?
> >
> > Thanks in advance for any and all advice on this, and sorry if this is a
> > FAQ. (I did a quick search on this topic, but could find nothing.)
> >
> > Anne
> >
> >
Received on Thu Jul 05 2001 - 09:42:52 CDT