Do not use the tablespace created for SDE metadata for any other purpose.
Best practice is to create one or more tablespaces to hold data, and one or
more users to own data, and then users to access data. Roles should be
created to manage access to tables, then users granted necessary roles.
I generally create several different tablespaces with different UNIFORM extent
sizes based on the "shirt size" of the table (small, medium, large, very-large).
This usually breaks down as "smaller than 5Mb", "5-20Mb", "20-200Mb", and
"200+Mb", but the number of available independent disks comes into play
as well. I also create a nominal "home tablespace" for user's scratch tables
(all 'real' data gets stored via DBTUNE keywords to the data tablespaces).
I used to create a tablespace for non-BLK raster data and one tablespace for
each large raster mosaic or catalog, but nowadays best practice is to keep
rasters as files on disk, not in the database.
- V