900626 Asset Configuration and Tracking Consolidation : Approaches
This page last changed on Nov 06, 2006 by graybeal.

There are three overarching approaches to this task:

1) Merge Make the necessary changes to merge the two databases (probably into SSDS) and make the merged data visible through the same interfaces (MS Access, SSDS) that are available now.

2) Synchronize Synchronize the two databases so that changes in each appear in the other (though not all fields have to appear in both). Perform synchronizations via triggers or DTS jobs as appropriate.
2a) Dual create Support new instrument entry on either database, synchronizing the entries as needed and validating on sync.
2b) Unicreate Support new instrument entry only on one database.

3) Sync-to-SSDS Push information from the Instru database on BOG to the SSDS database. Don't bother to update the BOG database with changes that have been made to the SSDS data. (This is like Paul "keeping his own copy," which is what we are doing today, but it provides SSDS with the information Paul enters.)

Option Name Pros Cons Comments
1 Merge fairly maintainable
minimizes duplicate info 		lots of merging required
requires significant control security
causes most change		 must track "devices of interest" to OSG
2 Synchronize simplifies interface work lots of model changes
triggers fear of changes
most state complexity		 checkpoints needed for some synchronized data
2a Sync-dual create most like current system for users lots more checkpointing  
2b Sync-unicreate simple to implement reduces functionality to other interface  
3 Sync-to-SSDS simplest number of changes
least OSG impact		 no 2-way interoperability could report differences
Document generated by Confluence on Feb 03, 2026 14:21