Migrating an ALRS from a file geodatabase to a multiuser geodatabase

Roads and Highways can be used in both file and multiuser enterprise geodatabases. Some users may need to create their ALRS, LRS Networks, events, and intersections in a file geodatabase to ensure data is created and configured by a single user. Once these elements are created, the user can migrate the ALRS, tables, and feature classes into a multiuser geodatabase to take advantage of multiple users editing data in the ALRS at the same time with the option of creating multiple versions. To properly migrate an ALRS and related data items between a file and multiuser geodatabase, follow the steps below.

1. Create the minimum schema, ALRS, LRS Networks, events, and intersections. For more information, see Creating and loading the ALRS, Event types, and Creating an LRS intersection class.
2. Once your ALRS is created, calibrated, and configured to your liking, prepare the target geodatabase where the ALRS, feature classes, and tables will be migrated.
3. Use the Feature Class to Geodatabase (multiple) geoprocessing tool to copy all the feature classes that participate in the ALRS from the source geodatabase to the target geodatabase. At a minimum, this should include the calibration points, centerline, redline, networks, events, and intersections feature classes, along with any additional feature classes participating in the ALRS.

   

   

   Note:

   The Feature Class to Geodatabase (multiple) geoprocessing tool can be opened by right-clicking the selected feature classes in the Catalog window and clicking Export > To Geodatabase (multiple) or by opening the ArcToolbox window, expanding the Conversion Tools toolbox, expanding the To Geodatabase toolset, and double-clicking Feature Class to Geodatabase (multiple).

4. Use the Table to Geodatabase (multiple) geoprocessing tool to copy all the tables that participate in the ALRS from the source geodatabase to the target geodatabase. At a minimum, this should include centerline sequence, route, LRS edit log, LRS event behavior, LRS locks, LRS metadata, and any lookup table configured, along with any additional tables participating in the ALRS.

   

   

   Note:

   The Table to Geodatabase (multiple) geoprocessing tool can be opened by right-clicking the selected tables in the Catalog window and clicking Export > To Geodatabase (multiple) or by opening the ArcToolbox window , expanding Conversion Tools, expanding the To Geodatabase toolset, and double-clicking Table to Geodatabase (multiple).

5. In the Catalog window, refresh the target geodatabase. The ALRS tree should appear with all networks, events, and intersections.

   

6. Verify that all necessary coded value domains have been copied to the target geodatabase. In the Catalog window, right-click the geodatabase and click Properties. Click the Domains tab and verify the following coded value domains have been copied over: dActivityType, dLRSNetworks, and dReferentMethod. If any of those domains are missing, make sure they are imported from the source geodatabase to the target geodatabase before proceeding. Verify that any additional subtypes or coded value domains used by the networks, events, or intersections were copied over as well.

   

7. Verify that all indexes are present on the feature classes and tables participating in the ALRS. For a list of indexes recommended for each item, see Data performance tips.
8. Register any feature class and table that participates in the ALRS as versioned, except for the LRS Event Behavior, LRS Locks, LRS Metadata, along with any lookup table being used by networks in the ALRS. To register a feature class or table as versioned, use the Register As Versioned geoprocessing tool.

   

   Note:

   The Register As Versioned geoprocessing tool can be opened by right-clicking the selected feature class/table in the Catalog window and clicking Manage > Register as Versioned or by opening ArcToolbox, expanding Data Management Tools, expanding Versions, and double-clicking Register As Versioned.

9. If you want to use editor tracking with intersections and any other feature classes and tables in your ALRS, enable it on all participating feature classes and tables. For more information about editor tracking, see Enable Editor Tracking.