I need to build a system whereby the user of a web map (the standard web map that ArcGIS Server Manager builds) can edit a feature class's attributes. The attribute will be a 'Comments' field. The feature class will be replaced quarterly but the 'Comments' field must persist across quarterly updates.

I am thinking to build a stand alone table in sde (MSSQL 2008) and let users of the web map update the feature class's 'Comments' field directly then have a db trigger fire which will write to the stand alone table.. the unique id of the record in the feature class and also the comments edit. This would be to retain the 'Comments' field apart from the feature class thus persisting the comments across quarterly updates of the feature classes.

I have already built the standard web map from AGS Manager and created the feature service of the feature class and tested the editing of a 'Comments' field. Now I am starting to build the persisted 'Comments' architecture.

Also, there may be multiple 'Comments' attributes inserted over time, I am uncertain as to whether I should have multiple 'Comments' fields in a stand alone table OR have multiple records in the stand alone table with each comment and the unique id and do a one-to-many join to return them in the web map. I also think deleting comments will be important.

Does anyone have any suggestions or tips or alternative approaches? If the T-SQL approach, are there any tips on T-SQL and SDE?


  • depending on your quarterly replace process I would create my own id field. As edits (export, delete, split) on the geometry will produce variations of the FID/OID. – Brad Nesom Aug 29 '11 at 13:43
  • looks like you're trying to create an audit trail. there is a lot of information bout that on the web. here's a gneration tool: codeproject.com/KB/database/AuditTrailGenerator.aspx – Steve Aug 29 '11 at 18:23
  • @Brad Nesom : the id field is from the vendor and is not the fid/oid. If they split a line, then I wouldn't know if the comments should stay associated with the record from the split that retained the id or the new record that got a new id or if original id is gone and now the comment is orphaned. I guess I should write more than just the id field (like the description of the record) so I would have some chance to find it later and also perhaps do backups of all those records which have a comments associated with it. Thanks for the opportunity to have a sounding board. – Justin Aug 29 '11 at 21:37
  • I have seen com objects written in arcmap to manage the orphans. The program warned that you were deleting a related object and asked if the orphan was to be deleted. – Brad Nesom Aug 30 '11 at 22:21

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.