![]() |
Telelogic SYNERGY (steve huntington) | ![]() |
Topic Title: Merging Synergy databases Topic Summary: Created On: 15-Jan-2004 21:42 Status: Read Only |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
For several years, we have developed separate products in independent Synergy databases. We now want to converge two of these products into a single suite, which means that we want to merge the two Synergy databases, complete with object histories, into a single database. There seem to be several ways to go about merging databases, all with significant drawbacks. - Use the migrate utility. This falls well short of the mark, since keeping object history is painful and it doesn't offer help with moving tasks, folders, or other meta-data to the new database. - Use the export/import tools. The problem here is that if I have two objects with the same four-part name, I can't have them both in the new database. In particular, tasks and folders are guaranteed to collide, since they are all named by sequential numbers. - Use DCM. This imposes a considerable financial impact, as well as adding complexity to our environment that we don't need once the merge is complete. Any thoughts on other ways to merge two databases? Thanks, Mike. |
|
![]() |
Telelogic SYNERGY
» SYNERGY/CM
»
Merging Synergy databases
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.