Migrate an LRS from a file geodatabase to a multiuser geodatabase

Available with Location Referencing license.

You may need to create a linear referencing system (LRS), LRS networks, LRS events, LRS intersections, domains, and attribute rules in a file geodatabase before moving the file geodatabase to a multiuser geodatabase to ensure that data is created and configured by a single user.

Once these elements are created in a file geodatabase, you can migrate the LRS, tables, feature classes, domains, and attribute rules into a multiuser geodatabase to use the multiuser versioned editing tools in ArcGIS Pro and in the Event Editor web app.

To migrate an LRS and related data items from a file geodatabase to a multiuser geodatabase, complete the following steps:

1. Create the minimum schema for the LRS, LRS Networks, LRS events, and LRS intersections in the file geodatabase.

   Note:

   The LRS will be created in a feature dataset. If your LRS was already created in ArcMap or in ArcGIS Pro 2.9 or an earlier version of ArcGIS Pro, you need to move all the feature classes that are part of the LRS into a single feature dataset.

2. Once the LRS is created, calibrated, and configured in the file geodatabase, prepare the target multiuser geodatabase for the LRS, feature classes, and tables you want to migrate, and set the connection file versioning type to branch.

   Note:

   Ensure that the connection file Versioning Type is set to Branch.

   Learn more about using the Geodatabase Connection Properties dialog box

   

3. In the Catalog pane , right-click and copy the LRS feature dataset that contains all the feature classes from the source geodatabase.

   

4. Paste the feature service into the root level of the target geodatabase.

   

5. Refresh the target geodatabase.

   The feature dataset with all the features classes are now in the target geodatabase. The tables managed by the LRS and the domains and attribute rules are also in the target geodatabase.

6. If other feature classes outside the feature dataset or tables not managed by the LRS weren't included, copy them from the source geodatabase to the target geodatabase.
7. Right-click the target geodatabase in the Contents pane, choose Data Design > Domains, and on the Domains tab, verify that the dActivityType, dLRSNetworks, and dReferentMethod coded value domains are in the target geodatabase.

   

   If any of the domains are missing, ensure that they are imported from the source geodatabase to the target geodatabase before proceeding.

   Note:

   The dLRSNetworks domain must be attached to the NetworkID field in the Centerline Sequence table and the Calibration Point and Redline feature classes. The dActivityType domain must be attached to the ActivityType field in the Redline feature class.

8. Verify that any additional subtypes, coded value domains, and attribute rules used by the networks, events, or intersections were copied.
9. Verify that all indexes are present in the feature classes and tables participating in the LRS. Use data performance tips as a guideline to properly tune the database.
10. To branch version the data in the enterprise geodatabase, ensure that the data meets the register a dataset as branch versioned requirements.
11. Once the data has finished copying into the enterprise geodatabase, register all the tables, feature classes, and feature datasets as versioned, with the exception of the LRS_Locks table, which must remain unversioned.

    Note:

    If the LRS was last accessed using ArcMap or ArcGIS Pro 2.5 or earlier, there are four tables with the LRS_ prefix (LRS_Edit Log, LRS_Event Behavior, LRS_Locks, and LRS_Metadata).

12. If the LRS was created in ArcMap or in ArcGIS Pro 2.6 or earlier , run the Modify LRS tool to update the LRS to work with the latest ArcGIS Pro version.

    Once the LRS is upgraded using the Modify LRS tool in ArcGIS Pro 2.6 or later, the LRS_Event_Behavior and LRS_Metadata tables are no longer used and can be removed.