Originally posted by Jr
[code]
create tablespace test datafile 'F:\ORACLE\ORADATA\ASP2\TEST.DBF'
size 1025M autoextend on next 101M maxsize unlimited
extent management local uniform size 1024M;

SQL> create tablespace test datafile 'F:\ORACLE\ORADATA\ASP2\TEST.DBF'
size 3072M autoextend on next 101M maxsize unlimited
extent management local uniform size 1024M;
If you are going to do this then you should change the next to reflect the size of your uniform extent. Like:

[code]
create tablespace test datafile 'F:\ORACLE\ORADATA\ASP2\TEST.DBF'
size 1025M autoextend on next 1025M maxsize unlimited
extent management local uniform size 1024M;

SQL> create tablespace test datafile 'F:\ORACLE\ORADATA\ASP2\TEST.DBF'
size 3072M autoextend on next 1025M maxsize unlimited
extent management local uniform size 1024M;


You should relize that anytime a table grows beyond 1gb or anytime you create a table you will allocate another 1gb of storage. Even for a 50K file. That is why my example specified 1mb or 10mb uniform extents. So that you can have many extents in the tablespaces without growing the table every time. But it really depends on how many tables you plan to store in this tablespace and how large each one will be. The way you have it setup the storage will not be very granular. Which may or may not be a problem. If you plan on storing a 1gb table in this tablespace you will not get any better performance with 1gb uniform extents as compared with eith 100mb or 10mb extents. Making a smaller uniform extent size will allow tables to grow by smaller chunks.