DBAsupport.com Forums - Powered by vBulletin
Results 1 to 2 of 2

Thread: Truncating, HW Mark, Indexes

  1. #1
    Join Date
    Nov 2001
    New Brunswick, NJ


    Hello All,

    I have a table that I want to keep as highly optimized as possible. I want to set up a job that will copy the table to a temporary table, truncate the original table to move the HW mark back, and then copy the original data back. Once done, I'll analyze and recompute statistics.

    Will doing this automatically rebuild the index?

    Are there any other things I should do to optimize my table?



  2. #2
    Join Date
    Nov 2000
    Pittsburgh, PA
    It sounds like a lot of work for very little gain. Use locally managed tablespaces. My preference with uniform allocation. Split up the tables among the tablespaces according to size and make the allocation size appropriate for the table. i.e. a 1gb table might be in a tablespace with 10M extents yielding 100 extents which are fine, and a 32K table might be in a tablespace with either a 32K or 64K extent size. which will give 1 extent which is also fine.

    But to spend time moving around data when your tables may not be fragmented sounds like busy work. If you have extra time keep learning it will pay off more than the reorg on your tables.

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