We currently have a Bulletin Board version under sde.default, and then edit versions under the Bulletin Board version. Our normal workflow is to reconcile/post the edit versions to the Bulletin Board during the day. At the end of the day the Bulletin Board is reconciled/posted with sde.default. Usually this works fine. We do have many (300+) long-term versions that can have work in-process for months. They are reconciled daily bia a batch reconcile tool. My question is this: Can we change the parent version on existing versions from the Bulletin Board to sde.default without having to post them? We would like to get rid of the Bulletin Board version because of ghost conflicts we are getting and go to a flat versioning structure.
while not supported, this can be done. I've done it before for other bulletin board folks.
1) test this! 2) take good backups 3) the trick is to get bulletin board and sde.default to be at the exact same state prior to re-parenting. This is achieved by posting and reconciling the in the appropriate order. 4) once they are at the same state (query sde.versions), you can update the attributes in sde.versions for the version which you'd like to reparent.
UPDATE sde.versions SET parent_name = 'DEFAULT', parent_owner = 'SDE', parent_version_id = 1 WHERE owner = 'CHILD OWNER' AND name ='CHILD VERSION NAME'; commit;
Thanks for the replies. We have had ghost conflicts appear about every 2 years and it's a real pain to clean up. We are at the point of desparation and willing to get rid of our bulletin board version. 🙂 I'll test out the process you suggested Anthony and see if I break anything. Of course, backups first!
I would encourage you to also contact support about your phantom conflicts. If there is a problem in the software that's causing this, we need to fix it. Or if it is a problem that happens with certain workflows, we need to document how to avoid it.