Home » RDBMS Server » Performance Tuning » Optimum value for INITIAL_EXTENT (oracle 9.2.0.8)
Optimum value for INITIAL_EXTENT [message #288442] Mon, 17 December 2007 10:12 Go to next message
arunprasad_bh
Messages: 32
Registered: June 2007
Member
Hi is there any method for setting INITIAL_EXTENT, and NEXT_EXTENT values for tablespaces in a Datawarehouse?

I got a tablespace with initial extent value of 128k and one with 5MB.

How do we know which one is good?

Re: Optimum value for INITIAL_EXTENT [message #288449 is a reply to message #288442] Mon, 17 December 2007 10:23 Go to previous messageGo to next message
Michel Cadot
Messages: 64103
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
It depends on your current data and the size it will grow.
I advice you to use system (autoallocate) managed tablespace (http://download.oracle.com/docs/cd/B19306_01/server.102/b14200/statements_7003.htm#i2150446) and don't care about next. Just put initial at the size of your current data (or estimated for a first load if you don't have any for the moment).

Regards
Michel
Re: Optimum value for INITIAL_EXTENT [message #288485 is a reply to message #288449] Mon, 17 December 2007 14:21 Go to previous message
andrew again
Messages: 2577
Registered: March 2000
Senior Member
Check with your DBA for guidelines on which tablespace to use. Sometimes tablespaces are created to keep small/medium/large segments in small/medium/large tablespaces to avoid space wastage or excessive extents. They could also be created to keep static and dynapic segments away from each other so that large static tables aren't backed up so often. There could be other reasons too like spreading IO, but that's a very long debate in itself...
Previous Topic: While SQL tuning : Is NULL, In vs Exists
Next Topic: Indexing for lookup tables
Goto Forum:
  


Current Time: Sat Dec 03 05:56:48 CST 2016

Total time taken to generate the page: 0.05206 seconds