ArcGIS Pro 2.9.5; Oracle 18c 10.7.1 eGDB:
Staff in my unit use an OS authentication .SDE connection when editing data. When using that connection, the user’s Windows/network username gets used in editor tracking fields: I.e. JSmith. That works as expected.
But when doing data maintenance tasks like table design changes, power users like me use a database connection. The .SDE connection uses an Oracle user/owner/schema called ENGINEERING. We need to use that connection to make table design changes, instead of the OS authentication connection, because the OS authentication connection doesn’t have privileges for making table design changes.
Often, data maintenance initiatives involve not only table design changes, but also editing tasks like batch populating a field. It isn’t realistic to expect the person to flip back and forth between the DB connection (table design changes) and the OS connection (editing) when performing complex data maintenance tasks. We’ve tried to tell power users to only use the OS connection to make edits, but people inevitably use the DB connection for field calculation edits, too.
The problem with using the DB connection for edits is we don’t know what person made the edits, we only know that the ENGINEERING DB connection was used for the edits, because editor tracking inserts ENGINEERING as the user name. That’s not very useful when we’re troubleshooting issues/trying to figure out who made the edit.
Idea: When editing using a DB connection, could editor tracking use the Pro licensing username, instead of the user/owner/schema name?
- JSmith (Pro licensing user, via AGOL or Portal licensing), or
- JSmith/ENGINEERING
But not just ENGINEERING.
Database users/privileges/connections aren’t my areas of expertise, so let me know if I’ve misunderstood something.
