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, or update the portal trace network owner. It is also important to be aware of the supported compatibility between ArcGIS clients and geodatabase datasets for the trace network.
Migrate a trace network dataset
Once a trace network is created and configured, there are scenarios that may require the dataset to be transferred between a file and enterprise geodatabase for staging and testing. The core copy tools can be used to move the feature dataset containing the trace network between geodatabases. To import data into a trace network, the Append tool can be used.
Upgrade a trace network
A trace network dataset must be upgraded to take advantage of new functionality by applying schema changes in the information model. The ArcGIS Pro client version determines whether an upgrade is necessary.
The ArcGIS Pro version you're using determines the trace network version of the trace network dataset that is created. The ArcGIS Pro version also determines whether the trace network dataset requires an upgrade. The table below lists the ArcGIS Pro release and corresponding Trace Network Version.
| ArcGIS Pro release | Trace Network Version |
|---|---|
2.6.x | 1 |
2.7.x | 2 |
2.8.x | 2 |
The version of the trace network can be viewed on the Trace Network tab of the Network Properties dialog box.
To upgrade a trace network dataset, use the Upgrade Dataset tool. Before the upgrade is attempted, however, the following must be done:
- Save all edits.
- Obtain an exclusive lock; close any active connections, including services.
- Disable the network topology.
When working with an enterprise geodatabase, 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 with the versioning type set as branch.
To review specific schema changes for each version, see Trace network upgrade history.
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 utility network dataset.
- The portal trace network owner is stored as metadata for a utility network. You can view this using the network properties when accessed 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.
ArcGIS platform compatibility
It is important to be aware of the compatibility between ArcGIS clients, the geodatabase, and the trace network dataset when working with various versions. Trace networks in an enterprise geodatabase use a services-based architecture and are dependent on both the ArcGIS Pro and ArcGIS Enterprise client versions to enable new functionality.
Functionality is dependent on the ArcGIS Pro client version alone when working with a single-user deployment of the trace network.
Learn more about client and geodatabase compatibility
Trace network version
When a trace network is created, the version of ArcGIS Pro used is recorded on the Network Properties dialog box. This is found in the General section of the Trace Network tab for the ArcGIS Pro Release property. The Trace Network Version value is determined by the version of ArcGIS Pro used to create or upgrade the trace network dataset.
As geodatabases and client software are designed to work together, it is recommended that you keep these versions in sync when possible. As a general rule for working with various versions, ArcGIS client applications (such as ArcGIS Pro and ArcGIS Enterprise) are backward compatible when working with the trace network:
- Later versions of ArcGIS Enterprise can share earlier versions of the trace network.
- Later versions of ArcGIS Pro can be used to view and edit earlier versions of the trace network.
Note:
Trace network version 1 is only supported in a file geodatabase.
The table below outlines the ArcGIS platform compatibility for a trace network.
- ArcGIS Pro version—The version used to create or upgrade a trace network. This determines the Trace Network Version value.
- Trace network version—The version of the trace network dataset.
- ArcGIS Enterprise version—The version of ArcGIS Enterprise that can be used to share a trace network. This applies only to trace networks created in the multiuser model.
| Trace network version | ArcGIS Pro version | ArcGIS Enterprise version |
|---|---|---|
1 | 2.6.x | N/A |
2 | 2.7.x | 10.9 and later |
2 | 2.8.x | 10.9 and later |