Tags: database, index, initial, mysql, oracle, parameters, provide, regarding, sql, storage, table, tables, values
INITIAL and NEXT values for table/index storage
Can you provide some tips regarding the initial and next parameters of table/index storage ? If I have some few small tables in the same tablespace (4k, 16k and 5k). Those tables will grow by 1 record each month. What would be initial and next values for them ? Is there a minimum value to use, for performance reasons ?
Tks in advance.
Leave a comment...
- 3 Comments
If you are using oracle 8i or 9i, you can use Locally Managed Tablespace to avoid this storage parameters problems. Also, if you use 9i release 2, you can even give segment management auto to the tablespace.#1; Sun, 24 Feb 2008 01:10:00 GMT
- Tablespaces are already created (not LMT), so I'll create the tables and must provide some INITIAL and NEXT values. Could you then help ?#2; Sun, 24 Feb 2008 01:11:00 GMT
- Probably one of the most quoted documents on the subject, and very applicable to your situation if you are not using locally managed tablespaces, is this one:
HOW TO STOP DEFRAGMENTING AND START LIVING: THE DEFINITIVE WORD ON FRAGMENTATION / Bhaskar Himatsingka, Oracle Corporation; Juan Loaiza, Oracle Corporation (Acrobat Reader Portable Document Format aka PDF)#3; Sun, 24 Feb 2008 01:12:00 GMT