Geodatabase replication requirements for Checkout / Check-in

MarkChilcott

Hi Peoples,

Are there any Geodatabase data preparation requirements for Checkout / Check-in replication to a file geodatabase?

Geodatabase replication requirements:
To be replicated, datasets must meet the following requirements:

• The database user must have write access to the data.
• All datasets must be from the same enterprise geodatabase.
• All data must be registered with traditional versioning; it cannot be versioned with the option to move edits to base.

But goes to then say:
Additional replication requirements apply based on the replication type:
Checkout/Check-in replication
You have the option of checking out nonversioned data or data that has been registered with traditional versioning.

For one-way and two-way replicas the GlobalID column must exist.
For one-way replication only, you can use archiving instead of versioning to keep track of replica changes.

I cannot see there are any requirements for data preparation on Checkout/check-in :

• data does not need to be registered as versioned
• does not need to have GlobalID
• does not need to be archive enabled

Is this correct?

 

References:

• https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/overview/replication-and-geodatabase-compatibility.htm
• https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/overview/prepare-data-for-replication.htm
• https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/overview/create-a-checkout-replica.htm
• https://desktop.arcgis.com/en/arcmap/latest/manage-data/geodatabases/preparing-data-for-replication.htm
• https://community.esri.com/t5/esri-training-documents/distributing-data-using-geodatabase-replication/ta-p/1042931

Cheers,

Mark