It's a violation of best practice to load spatial data as the 'sde' login, much the way you shouldn't do software development as 'root' or Administrator. Instead, create data management logins, schemas that match, and load data as that login. For example, if I have streets data managed by the Pavement department, I'll create a login called "pavement" and a schema "pavement" then load the data in the production database as "prod.pavement.streets".
Best practice also calls for role creation, with access rights granted by role to the feature classes. Then normal logins associated with individual department staff members can be granted appropriate roles by resource (GRANT pavement_editor TO bob_smith). It's also best practice to avoid using data owners in web application connections, so a "viewer_app" login/schema could be created, with an appropriate role (GRANT pavement_viewer TO viewer_app).
- V
