AUTOALLOCATE vs UNIFORM SIZE
RadekMar 25 2013 — edited Mar 27 2013Hi,
Let's take 11.2.0.3 as an example.
If I had, let's say, a table 1.005GB in size, why should I bother to use AUTOALLOCATE for its tablespace and waste disk space (only 5B used in last 64MB extent), if I could instead use 1005 extents x 1MB as UNIFORM SIZE.
Thus:
1. I don't waste disk space for the UNIFORM SIZE option.
2. Extents number makes no difference from performace view (ok, I don't drop and recreate this table), as extent is just a logical structure. I mean extent number don't matter.
3. I don't use parallel direct path inserts (no extent trimming), just the conventional insert.
4. I still take advantage over ...,64kb, 128kb... multi-block read
Shoud I apply this to every tablespace? Makes sense?
Or should I not bother and leave it all to oracle? (AUTOALLOCATE) ?