40M initial extent?!!??
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 6 of 6

Thread: 40M initial extent?!!??

  1. #1
    Join Date
    Nov 2000
    Location
    Baltimore, MD USA
    Posts
    1,339
    Okay, so I'm working with a new client, and remember that the admin side is not my strong suit, but...

    Amongst many other questionable settings, they have a 40M initial exten setting for their primary data tablespace. Actually, they have 2 primary tablespaces: a large and a small one - the large one has an initial extent of 100M!!!!

    Am I fully showing my ignorance or is this truly insane? I mean, it *is* a DSS database, but there are still some little code tables with less than 100 records that are in a tablespace with an initial extent size of 40M!!

    What could possibly be the reasoning behind such a thing?

    Help!

    - Chris

  2. #2
    Join Date
    Nov 2000
    Location
    greenwich.ct.us
    Posts
    9,095
    An initial extent of 40M is not unreasonable for a tablespace that will hold large objects. Code tables? Sounds like a waste to me. If they're worried about fragmentation, put the code tables in a seperate tablespace with more reasonable INITIAL and NEXT extents.
    Jeff Hunter
    marist89@yahoo.com
    http://marist89.blogspot.com/
    Get Firefox!
    "I pledge to stop eating sharks fin soup and will not do so under any circumstances."

  3. #3
    Join Date
    Jun 2000
    Location
    Madrid, Spain
    Posts
    7,448
    Last time when I was working with this database configured by people from Accenture I saw initial of 250MB and next of 500MB in an oltp database Waste of space (even thought the hd are cheap this is bad waste!)

  4. #4
    Join Date
    May 2000
    Location
    ATLANTA, GA, USA
    Posts
    3,136
    In general, the next extent size should match the next 6 months data on that table.
    The next extent size like 40MB / 250MB / 500MB is an estimation based on the past growth analysis.

  5. #5
    Join Date
    Jun 2000
    Location
    Madrid, Spain
    Posts
    7,448
    If I have a growth analysis I wouldnt even set next extent big I would simply create a big initial and set next equal to initial

  6. #6
    Join Date
    Aug 2000
    Posts
    194
    Could it be, they intended to create the smaller tables with the physical attributes specified explicitly. (say, Create table small_table bla bla STORAGE (INITIAL small_size) )

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