It's far easier to write about what's *right* about using the SDE user for spatial data:
1) Nothing.
But let me give some highlights:
1) Anyone with SDE user password can destroy the integrity of the instance (which is
also why it's unwise to make the 'SDE' user password 'sde')
2) The SDE tablespace should not be fragemented with spatial data (and vice versa)
3) Best practice involves using multiple users, with data tables owned by logical data
sources (e.g., PLANNING, WATER, TAXATION, BASEMAP), with login accounts for
individual users (no shared passwords), and roles to grant access by logical duties.
4) Only senior staff, trained in geodatabase design and organizational DBTUNE
implementation, should be permitted to create new tables with ownership accounts
(they'd also be required to perform necessary GRANTs to access roles). [This also
provides a way to prevent unintended datatypes from being used -- tables can be
developed in user accounts and standardized before being shared.]
Of course, implementing best practice also involves more active participation of "DBAs"
in the workings of the "GIS stuff", and requires that GIS staff have more access to
critical tools, like the command-line ArcSDE utilities.
- V
