Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here


Best type of index to use...?

Best type of index to use...?

Best type of index to use...?

Hi everyone

I have a situation where I'm processing the data in a large table using a PL/SQL routine. The processing has to happen in batches and when a record has been processed, a field in the table is updated to indicate this. The field in question (called PROCESSED) is a simple NUMBER(1) field, where 0 = not processed and 1 = processed. When the PL/SQL process is run, it selects records from the table that have not yet been processed, i.e. where PROCESSED = 0.

The table has around 16 million rows in it, and to start with it's fairly quick at selecting rows that haven't yet been processed. However, the more records that get processed, the longer it's taking to find records where PROCESSED = 0.

What I'm wondering is what type of index would be best on the PROCESSED field? I know bitmap indexes are good when there's a low cardinality, which there is in this case, but there are going to be a lot of updates, which I believe is not so good for bitmap indexes.

Any suggestions would be greatly appreciated


RE: Best type of index to use...?


The person who says it can't be done should not interrupt the person doing it. -- Chinese proverb

RE: Best type of index to use...?

bitmap is not a good idea for heavily updated tables. Use a regular btreve index.

Lead Application Developer
New York State, USA

RE: Best type of index to use...?

Can I just check you are using FORALL/BULK operations in your PL/SQL

In order to understand recursion, you must first understand recursion.

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close