I have an Esri geodatabase two-way replica set. I need to update the schema on both databases in the replica set. Esri describes doing this using ArcGIS schema tools (compare/export/import replica schema - see here).
I have control of both databases in the replica set and I would prefer to make a python script, which updates the schema and run that on both databases in the replica set.
Are there potential problems with applying the schema changes to both databases instead using Esri's schema tools?
No information available at this moment of X-ray for enterprise geodatabase. Please put your suggestion on Idea site "http://ideas.arcgis.com/" which has more chance of quick consideration if more people vote for this idea.
Please see the below link for schema changes Best Practices. It states " In general, it is best to avoid schema changes. Schema changes can lead to inconsistencies among replicas, and the extra task of applying schema changes can increase performance costs. However, there are cases when schema changes must be applied".
If it is absolutely necessary to change schema on replica data then please follow the procedure of export, compare and import schema changes tool. In this workflow, you can avoid duplication of your effort and maintain consistency in both parent and child geodatabase.
Reading about the process and Geoprocessing Tools available for this type of replica schema change synchronization in the Help, will there be / is planned any future role of X-Ray for ArcCatalog in this type of process when X-Ray is updated to support enterprise geodatabases?:
No information available at this moment of X-ray for enterprise geodatabase. Please put your suggestion on Idea site "http://ideas.arcgis.com/" which has more chance of quick consideration if more people vote for this idea.
