topic Traditional & Branch Versioning in the same database in Geodatabase Questions

Traditional & Branch Versioning in the same database

Anonymous User — Fri, 07 Jan 2022 19:52:06 GMT

Can we use both Traditional & Branch Versioning in the same enterprise database? I think the answer is yes, but I wonder how Reconcile/Posting would work. If you Reconcile/Post through a database connections would that only work for the Traditional features, and then Reconcile/Post through the service would only work for the Branch features? There wouldn't be any kind of conflict?

Also, since Replication doesn't work with Branch Versioning, has anyone found a good way to synchronize a Branched Versioned dataset to another enterprise database?

Re: Traditional & Branch Versioning in the same database

George_Thompson — Fri, 07 Jan 2022 20:45:31 GMT

Yes, Branch and Traditional versioning can be used in the same enterprise geodatabase. The features classes can only participate in one or the other, NOT both.

You would reconcile / post as normal, there would not be any conflict as they do not share feature classes that participate.

As for the replication, you can edit the branch versioned data via the web as it is a service based architecture (Web GIS). Is there a reason that you would need to replicate with this model?

Here are some great blogs to review:

https://www.esri.com/arcgis-blog/products/arcgis-enterprise/data-management/to-branch-or-not-to-branch/

https://www.esri.com/arcgis-blog/products/arcgis-enterprise/data-management/branch-versioning-setting-the-stage/

https://www.esri.com/arcgis-blog/products/arcgis-pro/data-management/version-administrator-for-branch-versioned-data/

https://community.esri.com/t5/geodatabase-questions/blog-discussion-branch-versioning/td-p/835462

Let us know if you have any other questions.

Re: Traditional & Branch Versioning in the same database

Anonymous User — Fri, 07 Jan 2022 21:08:52 GMT

Ok, thank you for confirming the versioning scenarios.

We want to replicate our data because we are creating a dev environment to run along side our production environment. Running both traditional and branching versioning isn't an issue, except that we want to replicate our Water UN. Which it seems like won't be possible.

Re: Traditional & Branch Versioning in the same database

George_Thompson — Fri, 07 Jan 2022 21:27:10 GMT

Many people just use DB backup / restore to "refresh" data in DEV from PROD.

You should be able to use branch versioning to edit / "share" your UN data.

Re: Traditional & Branch Versioning in the same database

Anonymous User — Mon, 10 Jan 2022 21:27:47 GMT

We want to Replicate our UN data onto a different database in order to test our new workflows and troubleshoot, not just simply sharing. We need to keep these databases separate but in sync.

It would be very useful to be able to replicate branch versioned data.

Re: Traditional & Branch Versioning in the same database

DanMoore — Thu, 27 Jan 2022 16:07:34 GMT

At this time, geodatabase replication is not supported for branch versioned data.

https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/overview/replication-and-geodatabase-compatibility.htm

One option that has been mentioned would be to utilize a distributed collaboration - https://www.esri.com/arcgis-blog/products/arcgis-enterprise/sharing-collaboration/dev-summit-2021-use-distributed-collaboration-to-edit-and-update-data-across-organizations/

Re: Traditional & Branch Versioning in the same database

Anonymous User — Thu, 27 Jan 2022 16:30:02 GMT

We currently use a Distributed Collaboration for other things. Unfortunately, even a one way sync seems to only be able to store the data in a data store. We are trying to build a complete dev environment, which means housing the dev data in an enterprise db.

So it seems to only way to create a 'replica' environment would be to export any branch versioned features to the dev environment. Which is a time intensive process.

Re: Traditional & Branch Versioning in the same database

SeanRedar — Fri, 24 Jun 2022 23:24:13 GMT

Question 1- is branch versioning available for layers published from a user managed data store? (assuming no).

Question 2 - given I have many feature classes (30+) I would like to publish with branch versioning enabled, is it recommended to publish each layer alone or several together, like in the case with have a particular business line that has many feature classes.

Re: Traditional & Branch Versioning in the same database

Sarah_of_Lubbock — Thu, 13 Oct 2022 15:01:05 GMT

I'm in the same situation.
I would like our Dev environment to be in sync with our daily data.
Is there a good solution to this?

Re: Traditional & Branch Versioning in the same database

MarceloMarques — Thu, 13 Oct 2022 18:26:05 GMT

You can use RDMBS replication technology - Oracle Golden Gate, Oracle Data Guard, SQL Server Always On, PostreSQL Slony, then you can keep the dev in sync with prod, but do you really want that? you could simply restore a database backup of prod into dev every week or so, your database administrator can help choose the best solution and even automate the process.

Re: Traditional & Branch Versioning in the same database

MarceloMarques — Thu, 13 Oct 2022 18:29:12 GMT

Question 1- is branch versioning available for layers published from a user managed data store? (assuming no).

Answer: No, you must have an Enterprise Geodatabase - Oracle, SQL Server, PostreSQL.

Answer: it depends on the size of each featureclass and the business case that you are trying to solve, I would group them by editing workflow and then decide if shall break into subgroups.

Re: Traditional & Branch Versioning in the same database

MarceloMarques — Thu, 13 Oct 2022 18:30:06 GMT

Re: Traditional & Branch Versioning in the same database

Scott_Wolfskill — Thu, 22 Dec 2022 19:29:48 GMT

I am in a similar situation, but with enterprise data being shared with a client via a feature service. We are utilizing branch verisioning to manage edits on our side and had originally envisioned having two way editing using a distributed collaboration between our enterprise portals. However, our client is on an earlier version of Server and cannot enter a two way editing relationship at this time. We instead passed the portal service through to AGOL to share via a partnered collaboration, which has been working well in a read only capacity.

The client still has the desire to edit the data and I had hoped a check out could be created from default so they could complete data edits and return them to us for check in. This is apparently not possible now, but it would be great to see this kind of functionality in the future. For now we are handling all edits for the client, which is acceptable, but it is limiting, and we would like to find a better solution for the future.

Does this group have any suggestions for this use case or see anything I am missing here?

Re: Traditional & Branch Versioning in the same database

MarceloMarques — Thu, 22 Dec 2022 19:49:36 GMT

1. Geodatabase Replication is not an option because you are using Pro Branch Versioning

Prepare data for replication—ArcGIS Pro | Documentation

Note: Branch versioned data and data registered with traditional versioning that uses the option to move edits to base are not supported with geodatabase replication in ArcGIS Pro.

2. Geodata service and Take data offline with feature service sync capability

This might be an option for you. Read more in the links below.

Geodata service—ArcGIS Server | Documentation for ArcGIS Enterprise

Take data offline with feature service sync capability

Introduction to distributed data—ArcGIS Pro | Documentation

3. FME Workbench + FME Server

and/or

ArcGIS Data Interoperability + Model Builder + ArcGIS Server Geoprocessing Service

you can customize and create your own tool to synchronize the data, using out of the box functionality.

I hope this helps.