Geodatabase Row Level Auditing

[MarkWilloughby]

We would like to implement auditing at our organization to track inserts and updates of geodatabase object geometry and attribute data in our existing geodatabases.

We already have roled based permissions implemented on our SDE (Oracle) feature datasets. We want to track changes at the row level by role.

How can this be accomplished? Would the overhead of the auditing processes be noticed by the end user?

Thanks.

[MarkWilloughby]

No one knows how to accomplish this?

[MohammadIshfaq]

You can do it with the Oracle Fine-Grained Auditing (FGA) feature but remember it is enabled only on mission-critical dataset as it has a higher performance hit.

[MarkWilloughby]

Isn't there something simpler that can be done instead of FGA?

[MarkWilloughby]

I wish to thank everyone for their assistance with this problem thus far.

[SeanGrant]

Here is a link to an ArcMap extension that enables feature classes and tables to track user edits at the feature/record level. : http://resources.arcgis.com/gallery/file/arcobjects-net-api/details?entryID=3CAECB94-1422-2418-7F19-...

Also, this type of functionality is being looked at for OOTB @ 10.1. See forum posting here: http://forums.arcgis.com/threads/20386-Hold-on-Date-and-User-when-Editing

Hope this helps,
Sean

[MarkWilloughby]

Our preference is a server side solution as opposed to a desktop solution. That being said, this is what we would like to have as columns in all of our feature attribute tables in the geodatabase:

-created_by (char)
-created_on (date)
-created_using (char)
-modified_by (char)
-modified_on (date)
-modified_using (char)
-what_changed (char)

I'm not familiar with the 'under the hood' aspects of SDE but I would like to point our DBA to the tables that would need to be monitored using insert or update triggers to populate the above listed columns.

We want to track changes to both feature attributes and feature geometry and record if only the attributes, only the geometry or both the attributes and geometry changed during an edit session.

Can this be done without interfering with the ordinary operation of versioned SDE geodatabases?

[MarkWilloughby]

Is there a consultant out there that might be able to assist or at the very least, indicate that what we want to accomplish is feasible?

Or in the alternative, can any one tell me if the ESRI Enterprise Solutions Group has implemented a similar solution?