Home » RDBMS Server » Server Administration » max number of extents for individual objects
max number of extents for individual objects [message #180944] Wed, 05 July 2006 23:04 Go to next message
rs350z
Messages: 2
Registered: July 2006
Location: oregon
Junior Member
how many extents would an object have to have to be extreme? in my opinion, i would like to keep them to a maximum of 1000 to 2000 but i know of companies that have 30,000, 40,000, and even up to 90,000 extents for individual objects. these companies have indicated that the number of extents does not matter any longer. your opinions.
thanks
Re: max number of extents for individual objects [message #180980 is a reply to message #180944] Thu, 06 July 2006 02:50 Go to previous messageGo to next message
JSI2001
Messages: 1016
Registered: March 2005
Location: Scotland
Senior Member
An object would have as many extents as were required to store the requisite data.

Quote:


in my opinion, i would like to keep them to a maximum of 1000 to 2000



So in a segment with an extent size of say 64k block size 4k avg row length 1k, what would you do when your table exceeds the relatively small number of rows and passes your threshold of 2000 extents? Delete the rows?

Jim

Re: max number of extents for individual objects [message #181000 is a reply to message #180980] Thu, 06 July 2006 04:31 Go to previous messageGo to next message
rs350z
Messages: 2
Registered: July 2006
Location: oregon
Junior Member
to keep the extents manageable, i would adjust the size of the extents. there are 3 extent sizes i would use for all of my tablespaces and by using these sizes, you would keep the maximum number of extents below 2000. for example, i have used 128mb extent sizes for quite a few very large tables. you only need to make sure that the extent size is a multiple of your block size.
Re: max number of extents for individual objects [message #181021 is a reply to message #181000] Thu, 06 July 2006 06:18 Go to previous message
Mahesh Rajendran
Messages: 10707
Registered: March 2002
Location: oracleDocoVille
Senior Member
Account Moderator
>>to keep the extents manageable
What exact kind of 'management' would you do here ? Could you explain?
LMT will take care of that (with uniform extent size).
1000 or 100,000 or a million. Let it be (unless you would drop/rebuild or issue a related DDL too frequently or something like that. By the way, how frequently would you do those in a production environment?).
The following discussion in askTom would be a very good read.

http://asktom.oracle.com/pls/ask/f?p=4950:8:::::F4950_P8_DISPLAYID:730289259844

Long story short,
Number of extents no longer matter ( to be precise, in most of the cases like performance and 'management').

[Updated on: Thu, 06 July 2006 06:21]

Report message to a moderator

Previous Topic: difference between normal and 'as sysdba'
Next Topic: Upgrade of oracle 8i db
Goto Forum:
  


Current Time: Fri Sep 20 10:23:45 CDT 2024