You are setting yourself up for issues in the future, but it is possible to maintain a simple feature class exclusively from SQL. "Simple feature class" means:
- Table is registered with ArcSDE with a USER-set registered rowid (sdelayer -o register -C objid,USER...)
- Feature class is NOT versioned
- Feature class is NOT archived
- Feature class does NOT participate in geodatabase behaviors (relationship classes, feature datasets,...)
In essense, just a stripped down, native table with geometry (SDE.ST_GEOMETRY or MMDSYS.SDO_GEOMETRY).
It's theoretically possible to not trash tables with SDE-set rowids, if you honor all the restrictions in ID allocation, but that would likely tempt you into something which would regularly corrupt your geodatabase.
- V