Scratch (Transient) Table
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 8 of 8

Thread: Scratch (Transient) Table

  1. #1
    Join Date
    Apr 2002
    Location
    Shenzhen, China
    Posts
    327

    Scratch (Transient) Table

    We have a table of MEMBERS_ONLINE in a BBS application, and this table will have lots of DMLs, say 3 insert and 3 delete and 9 update per second, and the total rows number keeps on about 3,000.

    What's your opinion to deal with it? I think Oracle is very inefficient in this case cause of undo and redo records generated along, and temporary table is impossible here for every session need to query this table.

    I guess that a global memory collection maintained by JSP program would be a feasible solution?
    Last edited by Calvin_Qiu; 04-05-2003 at 04:01 AM.
    Oracle Certified Master - September, 2003, the Second OCM in China
    *** LOOKING for PART TIME JOB***
    Data Warehouse & Business Intelligence Expert
    MCSE, CCNA, SCJP, SCSA from 1998

  2. #2
    Join Date
    Aug 2002
    Location
    Colorado Springs
    Posts
    5,253

    Re: Scratch (Transient) Table

    [QUOTE] 3 insert and 3 delete and 9 update per second, and the total rows number keeps on about 3,000./QUOTE]

    This is trivial. Just use a regular table.
    David Aldridge,
    "The Oracle Sponge"

    Senior Manager, Business Intelligence Development
    XM Satellite Radio
    Washington, DC

    Oracle ACE

  3. #3
    Join Date
    Apr 2002
    Location
    Shenzhen, China
    Posts
    327
    That does throw out at least 24 changes on data block, undo block, and redo block, and this table is not crucial table, just for temporary application data. Do you think it is worthwhile?
    Oracle Certified Master - September, 2003, the Second OCM in China
    *** LOOKING for PART TIME JOB***
    Data Warehouse & Business Intelligence Expert
    MCSE, CCNA, SCJP, SCSA from 1998

  4. #4
    Join Date
    Aug 2002
    Location
    Colorado Springs
    Posts
    5,253
    You tell me -- does your application need it?
    David Aldridge,
    "The Oracle Sponge"

    Senior Manager, Business Intelligence Development
    XM Satellite Radio
    Washington, DC

    Oracle ACE

  5. #5
    Join Date
    Mar 2002
    Posts
    301
    Hi,

    If it is only a temporary table then you can create / change the table as "NOLOGGING" so that the amount of redo / undo generated will be very minimal

    HTH.
    Say No To Plastics

  6. #6
    Join Date
    Aug 2002
    Location
    Colorado Springs
    Posts
    5,253
    Only true in very limited circumstances -- probably not in this case. I think that NOLOGGING would have no effect here.
    David Aldridge,
    "The Oracle Sponge"

    Senior Manager, Business Intelligence Development
    XM Satellite Radio
    Washington, DC

    Oracle ACE

  7. #7
    Join Date
    Apr 2002
    Location
    Shenzhen, China
    Posts
    327
    NOLOGGING isn't helpful for these changes are one by one unless it is stored in temporary tablespace, but it is a global table which need to be queried by all session.

    I'm thinking if it is possible having a global object maintained by JSP routine running in web server instead of a database table. It would be simply a memory data structure.
    Last edited by Calvin_Qiu; 04-07-2003 at 10:12 PM.
    Oracle Certified Master - September, 2003, the Second OCM in China
    *** LOOKING for PART TIME JOB***
    Data Warehouse & Business Intelligence Expert
    MCSE, CCNA, SCJP, SCSA from 1998

  8. #8
    hi, I think you can just keep this table and alter the initial and max trans for this table.
    Make sure your index is in good state.
    www.cnoug.org

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  


Click Here to Expand Forum to Full Width