It is not recommended to load data into the SDE user tablespace.
When the SDE user is created, the SDE user has a default tablespace. The tablespace is designed for the storage of the ArcSDE and Geodatabase schemas. Loading data into the SDE user tablespace is the same to ArcSDE as loading data into the SYSTEM tablespace is to Oracle. It should be avoided.
The storing of spatial data in the SDE user tablespace leads to suboptimal performance of spatial data due to:
- fragmentation of the SDE tablespace.
- potential to crash the ArcSDE if the tablespace fills up.
- possible contention on the storage space.
When a user connects for the first time, the SDE_LOGFILE tables are created to store any user selection. It is not unusual for users to select 100K features. If the SDE user were to make this selection, 100K entries would be written to the log files, potentially in the SDE user tablespace. This should be avoided.