never want to use to for invoice numbers if you need to account for every
value. An example of when a sequence number might be lost is if a
transaction grabs a number and then does a rollback instead of committing.
Using one sequence can cause a resource contention, a "Hot Spot", issue if
you have too many things trying to access the sequence at similar times.
If you are worried about a B-tree index that is adding nearly sequential
data from becoming "out of balance" or lopsided you can use a reverse key
index in Oracle.
-Kore Peterson
"Deanna Schneider"
<[EMAIL PROTECTED] To: CF-Talk <[EMAIL PROTECTED]>
.uwex.edu> cc:
Subject: Re: Generating Primary Key in Oracle (part 2)
12/05/2003 11:03 AM
Please respond to
cf-talk
Blah! That would be an issue. But, it's not one that I'll ever have to deal
with, as we don't do accounting type stuff. But, good to know for future
reference.
> An example of where a common seq would cause problems is if the seq
number
> becomes an invoice number, and the audit trail requires that every number
in
> a sequence be accounted for. This is pretty outmoded thinking now, but
some
> auditors still stick to the rule - "I want to see every invoice, IN
> SEQUENCE, filed in those binders there to verify they are all accounted
> for."
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
