Create Replica (Data Management Tools)
Summary
Creates a replica in a geodatabase from a specified list of feature classes, layers, datasets, and tables in an enterprise geodatabase.
Usage
All datasets must be from the same source (parent) enterprise geodatabase.
Confirm that the field names in the source (parent) geodatabase do not exceed the maximum field name length supported in the database where the target (child) geodatabase is stored. If the target geodatabase cannot store all the characters, the field names will be truncated. This results in field names that do not match. Subsequent replica synchronizations will not transfer edits between those fields due to the mismatched field names.
The data that will be replicated must be registered as traditional versioned but not with the option to move edits to base.
The connected database user must also have write permissions to the data.
For two-way and both types of one-way replicas, all datasets must have a GlobalID column.
For check-out and one-way replicas, the child replica geodatabase can be an enterprise or file geodatabase.
For two-way and one-way child-to-parent replicas, the child geodatabase must be an enterprise geodatabase.
To use archiving for one-way replicas, the parent workspace must be connected to the default version. For one-way child-to-parent replicas, the child workspace must be connected to the default version.
You can replicate all of the data in the datasets or replicate subsets of the data. You can specify the subsets of data to be replicated in the following ways:
Use definition queries on the data.
Specify an extent using the geoprocessing Extent environment setting.
Use the Replica Geometry Features parameter in this tool.
For tables, the default filter is schema only; only the schema for the table will be replicated. To apply a filter to a table, first create a table view with the appropriate filters. Then use this result as input to this tool. See Make Table View for more information. For more information about filters and replication, see Prepare data for replication.
You can use the Replica Geometry Features parameter or the Extent environment setting to define the replica geometry.
If a value is provided for the Replica Geometry Features parameter, it will be used as the replica geometry.
If no value is provided for the Replica Geometry Features parameter, the Extent environment will be used as the replica geometry.
If neither the Replica Geometry Features parameter value nor the Extent environment is specified, the full extent of the data will be used.
The replica geometry features can be points, lines, or polygons.
A feature layer used for the replica geometry features can contain one or more features. If there is more than one, the geometries are merged, and only data that intersects the merged geometries will be replicated.
If filters (such as selection or definition query) have been defined on the replica geometry features, only features that satisfy these filters will be used to define the replica geometry. See Prepare data for replication for more information.
The Re-use Schema parameter options are only available for checkout replicas.
Parameters
| Label | Explanation | Data type |
|---|---|---|
|
Replica Datasets |
The data that will be replicated. This list consists of layers and tables referencing versioned, editable data from an enterprise geodatabase. |
Table View; Dataset |
|
Replica Type |
Specifies the type of replica that will be created.
|
String |
|
Geodatabase to replicate data to (Optional) |
The geodatabase that will host the child replica. Geodata services are used to represent remote geodatabases. The geodatabase can be an enterprise or file geodatabase. For two-way and one-way-child-to-parent replicas, the child geodatabase must be an enterprise geodatabase. For one-way and checkout replicas, the geodatabase can be a file or enterprise geodatabase. This parameter is required if the Output Type parameter is set to Geodatabase. |
Workspace; GeoDataServer |
|
Replica Name |
The name that identifies the replica. |
String |
|
Replica Access Type (Optional) |
Specifies the type of replica access.
|
String |
|
Initial Data Sender (Optional) |
Specifies which replica will send changes when in disconnected mode. If you are working in a connected mode, this parameter is inconsequential. This ensures that the relative replica will not send updates until the changes are first received from the initial data sender.
|
String |
|
Expand Feature Classes and Tables (Optional) |
Specifies whether expanded feature classes and tables—such as those in networks, topologies, or relationship classes—will be added.
|
String |
|
Re-use Schema (Optional) |
Specifies whether a geodatabase that contains the schema of the data to be replicated will be reused. This reduces the amount of time required to replicate the data. This parameter is only available for checkout replicas.
|
String |
|
Replicate Related Data (Optional) |
Specifies whether rows related to rows existing in the replica will be replicated. For example, a feature (f1) is inside the replication filter and a related feature (f2) from another class is outside the filter. Feature f2 will be included in the replica if you choose to get related data.
|
String |
|
Replica Geometry Features (Optional) |
The features that will be used to define the area to replicate. |
Feature Layer |
|
Use archiving to track changes for 1 way replication (Optional) |
Specifies whether the archive class will be used to track changes instead of the versioning delta tables. This is only available for one-way replicas.
|
Boolean |
|
Register existing data only (Optional) |
Specifies whether existing data in the child geodatabase will be used to register the replica datasets. The datasets in the child geodatabase must have the same names as the datasets in the parent geodatabase.
|
Boolean |
|
Output Type (Optional) |
Specifies the output type of the data that will be replicated.
|
String |
|
XML file to replicate data to (Optional) |
The name and location of the This parameter is required if the Output Type parameter is set to Xml file. |
File |
|
All records for tables (Optional) |
Specifies whether all records or only the schema will be copied to the child geodatabase for tables that do not have filters applied (such as selections or definition queries). Tables with applied filters will be honored.
|
Boolean |
|
File geodatabase location (Optional) |
The location of the file geodatabase that will be created to host the child replica. This parameter is required if the Output Type parameter is set to New file geodatabase and is only valid for one-way and checkout replicas. |
Folder |
|
File geodatabase name (Optional) |
The name of the file geodatabase that will be created to host the child replica. This parameter is required if the Output Type parameter is set to New file geodatabase and is only valid for one-way and checkout replicas. |
String |
|
Geometry Filter Type (Optional) |
Specifies the spatial relationship between the Replica Datasets and Replica Geometry Features parameter values. The spatial relationship is applied to data in an extent defined by the Replica Geometry Features parameter value.
|
String |
|
Replicate (Optional) |
Specifies whether the Replica Datasets parameter value will be replicated with all features or using the schema only. The parameter is available when the Replica Type parameter value is a check out replica.
|
String |
Derived output
| Label | Explanation | Data type |
|---|---|---|
|
Output Child Workspace |
The output child geodatabase. |
Workspace |
|
Output Replica Name |
The name of the output replica. |
String |
Environments
Current Workspace, Output CONFIG Keyword, Extent, Scratch Workspace
Licensing information
- Basic: No
- Standard: Yes
- Advanced: Yes