Available with Standard or Advanced license.
After a trace network is created and configured in a geodatabase, additional administration tasks are necessary, depending on your organizational needs. Dataset administration tasks for a trace network can include the need to migrate the dataset between geodatabases, upgrade the dataset, or update the portal trace network owner. It is also important to be aware of the supported compatibility between ArcGIS clients and geodatabase datasets such as the trace network.
Trace network dataset migration
After a trace network is created and configured, there may be scenarios that require the dataset to be transferred between a file geodatabase and a mobile or enterprise geodatabase for staging and testing. The trace network dataset does not currently support migration between geodatabases using the core copy and paste data transfer tools in ArcGIS Pro; however, other options are available to migrate your trace network data.
You can migrate your trace network across geodatabases at the feature dataset level by right-clicking the feature dataset on the Project tab of the Catalog pane to export and import an XML workspace document. Alternatively, you can use the Export XML Workspace Document and Import XML Workspace Document geoprocessing tools. Using these tools, you can export data or export only the schema. The Schema only option of the Export Options parameter exports the trace network schema along with existing network diagram templates and named trace configurations. The default Data option also exports the data and network diagrams.
Keep the following in mind when migrating a trace network using an XML workspace document:
- The trace network version is maintained in the output geodatabase.
- The network topology of the output dataset is disabled.
- The diagram consistency state of the exported network diagrams is set as inconsistent.
- You can export an XML workspace document in the .zip file format to create a smaller, more portable file.
Caution:
The Export XML Workspace Document tool is not recommended for copying large amounts of geodatabase data with the default Data option. As an alternative, you can use an XML workspace document to transfer the dataset's schema between geodatabases and use the Append tool to import the data.
It is recommended that you enable the network topology and update any network diagrams after importing an XML workspace document into a new geodatabase.
Update the portal trace network owner
When working with an enterprise geodatabase, a trace network dataset has two owners that are used to control access for administrative tasks. In addition to the database user who creates a trace network, the active portal user account is recorded as the portal trace network owner. When a trace network is created, these owners are determined based on the user accounts for the database connection and active ArcGIS Enterprise portal.
- The database trace network owner is recorded as part of the fully qualified name of the trace network dataset.
- The portal trace network owner is stored as metadata for a trace network. You can view this metadata using the network properties when you access it using a database connection as the data owner.
While the data owner (database user) cannot be updated without re-creating the data, you can update the portal dataset owner for a trace network. If the existing portal trace network owner leaves the organization, you must change the portal owner to another user. This user must comply with the same user type and privilege as the original owner. Refer to the Update Portal Dataset Owner tool for more information.
After the portal owner is updated for the dataset, you must also change item ownership for any existing portal items for map, image, and feature layers.
Trace network compatibility
It is important to be aware of the compatibility between ArcGIS clients, the geodatabase, and the version of the trace network dataset when working with mixed releases. In an enterprise deployment of the trace network that uses a services-based architecture, the available range of capabilities are dependent on the ArcGIS Pro and ArcGIS Enterprise releases as well as the version of the trace network. In a single-user deployment of the trace network, functionality is dependent on the ArcGIS Pro release and the version of the trace network. While not required, it is recommended that you keep the versions in sync when possible, as these pieces of software are designed to work together..
Trace network version
The Trace Network Version value indicates the schema version of the trace network dataset and is recorded in the Trace Network tab of the Trace Network Properties dialog box.
Create or upgrade a trace network
A trace network can be created in an enterprise, file, or mobile geodatabase. To create a trace network in an enterprise geodatabase, the database platform must meet the minimum release. For more information, refer to the database requirements for ArcGIS Pro.
| Database platform | Minimum release |
|---|---|
| SQL Server | SQL Server 2017 |
| Oracle | Oracle 19.3.0.0 |
| PostgreSQL | PostgreSQL 13.13 |
| SAP HANA | HANA 2.0 SPS05 |
Beginning with ArcGIS Pro 3.3, the version of ArcGIS Pro and ArcGIS Enterprise determine the Trace Network Version value when creating or upgrading a trace network in an enterprise deployment:
- When using an enterprise geodatabase, the version of ArcGIS Pro and the connected portal's federated servers are used to determine the compatible Trace Network Version value.
Note:
When working in a multimachine deployment in which various versions of ArcGIS Enterprise are installed, all of the portal's federated servers are checked to create a trace network version that is compatible with the highest release available.
- When working with a single-user deployment of the trace network, the version of ArcGIS Pro determines the compatible Trace Network Version value.
An upgrade of the trace network dataset is needed to take advantage of new functionality introduced through schema changes in the information model. To upgrade a trace network dataset, use the Upgrade Dataset tool.
The upgrade process increments the trace network version number. Upgrades are cumulative between versions and include changes from skipped versions. For example, if you upgrade the trace network from Trace Network Version 2 to Trace Network Version 4, all schema changes for versions 3 and 4 are included.
Before the upgrade is attempted, the following must be completed:
- Save all edits.
- Obtain an exclusive lock by closing any active connections, including services.
- Disable the network topology.
When working with an enterprise deployment, the following requirements must be met:
The geodatabase version must be 10.8.1.2.6 or later.
- The input for the Dataset to upgrade parameter must be from a database connection established as the database trace network owner with the versioning type set as branch.
- The active portal account must be the portal trace network owner.
The following table outlines the version of the trace network created with different releases of ArcGIS Pro and ArcGIS Enterprise when creating or upgrading the trace network dataset.
| Trace Network Version | Compatible ArcGIS Pro version | Compatible ArcGIS Enterprise version |
|---|---|---|
1 | 2.6 and later | Note:Trace Network Version 1 is not supported in an enterprise deployment. |
2 | 2.7 and later | 10.9.1 and later |
3 | 3.0 and later | 11 and later |
4 | 3.3 and later | 11.3 and later |
Using the above matrix, the following scenarios help illustrate how the Trace Network Version value is determined on creation and upgrade:
- Creating a trace network in an enterprise deployment with ArcGIS Pro 3.3 and ArcGIS Enterprise 11.3 creates a Trace Network Version 4.
- Creating a trace network in an enterprise deployment with ArcGIS Pro 3.3 and ArcGIS Enterprise 10.9.1, creates a Trace Network Version 2.
- Upgrading a Trace Network Version 2 in an enterprise deployment using ArcGIS Pro 3.3 and ArcGIS Enterprise 11.1 result in the creation of a Trace Network Version 3.
- Creating or upgrading a trace network in a single-user deployment with ArcGIS Pro 3.3 creates a Trace Network Version 4.
Consume and work with a trace network
As a general rule for working with mixed releases and the trace network, ArcGIS client applications (such as ArcGIS Pro and ArcGIS Enterprise) are backward compatible. In other words, later versions of ArcGIS Pro and ArcGIS Enterprise can access, consume, edit, and share earlier versions of the trace network. The following examples help to illustrate backward compatibility with the trace network:
- ArcGIS Pro 3.3 can access, edit, and share a Trace Network Version 4 in ArcGIS Enterprise 11.3.
- ArcGIS Pro 3.2 can access, edit, and share a Trace Network Version 2 in ArcGIS Enterprise 10.9.1.
- ArcGIS Pro 3.1 can access, edit, and share a Trace Network Version 3 in ArcGIS Enterprise 11.1.
In an enterprise deployment, earlier versions of ArcGIS Pro can be used to access and edit later versions of the trace network through a service as long as the trace network version is supported by the ArcGIS Enterprise release and does not participate in newer functionality.
Note:
Earlier client software releases may not be able open or work with trace network datasets that participate in newer functionality. For example, ArcGIS Enterprise 10.9 cannot be used to share a Trace Network Version 3, and you cannot consume a file geodatabase containing a Trace Network Version 4 using ArcGIS Pro 2.7.