Geoprocessing tool reference > Data Management toolbox > Distributed Geodatabase toolset > Tools
Synchronize Changes (Data Management) (ArcInfo and ArcEditor only) |
|
|
Release 9.2
Last modified November 29, 2010 |
Print all topics in : "Tools" |
Synchronizes updates between 2 replica geodatabases in a direction specified by the user.
Learn more about data synchronization
Usage tips
-
The Advanced Settings section allows you to over-ride the default conflict resolution policy. This is set when you choose or change a direction for the synchronization.
-
Once synchronized, the changes (edits) will be reflected in the master geodatabase and viewable by all users.
-
The following environment settings affect this tool: workspace, scratch workspace, and Configuration keyword.
Command line syntax
An overview of the Command Line window
SynchronizeChanges_management <geodatabase_1> <in_replica> <geodatabase_2> {FROM_GEODATABASE_1_TO_2 | FROM_GEODATABASE_2_TO_1 | BOTH_DIRECTIONS} {MANUAL | IN_FAVOR_OF_GDB1 | IN_FAVOR_OF_GDB2} {BY_OBJECT | BY_ATTRIBUTE} {reconcile}
| Parameter | Explanation | Data Type |
| <geodatabase_1> |
The geodatabase hosting the replica to synchronize. The geodatabase may be local or remote. |
Workspace | GeoDataServer|GPComposite type |
| <in_replica> |
A valid replica with a parent contained within one input geodatabase and a child in the other input geodatabase. |
String |
| <geodatabase_2> |
The geodatabase hosting the relative replica. The geodatabase may be local or remote. |
Workspace | GeoDataServer|GPComposite type |
| {FROM_GEODATABASE_1_TO_2 | FROM_GEODATABASE_2_TO_1 | BOTH_DIRECTIONS} |
The direction you want changes to be sent in: from geodatabase 1 to geodatabase 2, from geodatabase 2 to geodatabase 1, or to send changes in both directions. For check out/check in replicas or one way replicas there is only one appropriate direction. If the replica is two way then any of the three choices are available. |
String |
| {MANUAL | IN_FAVOR_OF_GDB1 | IN_FAVOR_OF_GDB2} |
Specifies how conflicts are resolved when they are encountered. MANUAL - manually resolve conflicts in the versioning reconcile environment. IN_FAVOR_OF_GDB1- conflicts resolve in favor of the <geodatabase_1>. IN_FAVOR_OF_GDB2- conflicts resolve in favor of the <geodatabase_2>. |
String |
| {BY_OBJECT | BY_ATTRIBUTE} |
Specifies how you would like to define conflicts: By Object or By Attribute. Defining conflicts by object will detect conflicts by row while defining them by attribute detects conflicts by column. |
String |
| {reconcile} |
Indicates whether to automatically reconcile once data changes are sent to the parent replica if there are no conflicts present. This option is only available for check out/check in replicas.
|
Boolean |
Command line example
SynchronizeChanges d:\workspace.mdb MyReplica1 "Database Connections\Connection to workspace.sde" GEODATABASE_1_TO_2 IN_FAVOR_OF_GDB1 TRUE
Scripting syntax
About getting started with writing geoprocessing scripts
SynchronizeChanges_management (geodatabase_1, in_replica, geodatabase_2, in_direction, conflict_policy, conflict_definition, reconcile)
| Parameter | Explanation | Data Type |
| geodatabase_1 (Required) |
The geodatabase hosting the replica to synchronize. The geodatabase may be local or remote. |
Workspace | GeoDataServer|GPComposite type |
| in_replica (Required) |
A valid replica with a parent contained within one input geodatabase and a child in the other input geodatabase. |
String |
| geodatabase_2 (Required) |
The geodatabase hosting the relative replica. The geodatabase may be local or remote. |
Workspace | GeoDataServer|GPComposite type |
| in_direction (Optional) |
The direction you want changes to be sent in: from geodatabase 1 to geodatabase 2, from geodatabase 2 to geodatabase 1, or to send changes in both directions. For check out/check in replicas or one way replicas there is only one appropriate direction. If the replica is two way then any of the three choices are available. |
String |
| conflict_policy (Optional) |
Specifies how conflicts are resolved when they are encountered. MANUAL - manually resolve conflicts in the versioning reconcile environment. IN_FAVOR_OF_GDB1- conflicts resolve in favor of the <geodatabase_1>. IN_FAVOR_OF_GDB2- conflicts resolve in favor of the <geodatabase_2>. |
String |
| conflict_definition (Optional) |
Specifies how you would like to define conflicts: By Object or By Attribute. Defining conflicts by object will detect conflicts by row while defining them by attribute detects conflicts by column. |
String |
| reconcile (Optional) |
Indicates whether to automatically reconcile once data changes are sent to the parent replica if there are no conflicts present. This option is only available for check out/check in replicas.
|
Boolean |
Data types for geoprocessing tool parameters
Script example
# Create the Geoprocessor object
import arcgisscripting, sys, scripting, os
gp = arcgisscripting.create()
# Set the necessary product code
gp.SetProduct("ArcInfo")
# Load required toolboxes...
gp.AddToolbox("Data Management Tools.tbx")
# Process: Synchronize Changes...
gp.SynchronizeChanges("d:\workspace.mdb", "MyReplica1", "Database Connections\Connection to workspace.sde", "GEODATABASE_1_TO_2", "IN_FAVOR_OF_GDB1", "TRUE")