Migrating databases to InfoWorks WS Pro

This topic describes the process of migrating a database from InfoWorks WS to InfoWorks WS Pro.

Since the database technology used by InfoWorks WS Pro is completely different to that used in InfoWorks WS , it is necessary to go through a migration process, where all the relevant data from the original database is collected in a single file. This file can then be imported into the new database format.

The process of creating the migration file is the same for all supported InfoWorks WS database types: JET, Oracle and SQL Server. To create a migration file, it is necessary to be running InfoWorks WS 17.0.2 or later. This may require your existing database to be updated to allow the newer application to open it. The update process will depend on the database type and is not documented here.

Some model objects such as baselines refer to other objects (via drop targets). It is possible that the baseline and referenced objects exist in different model groups. If one object references a second object (via a drop target) then both objects must be selected for migration. If the two objects are in the same model group then by default they will both be selected, and there is no problem. Problems may arise if a subset of model groups is selected or if a subset of objects within a model group is selected. In this case, you must either know which objects reference other objects, or you must use the alternative migration method using an intermediate JET database.

This is the procedure for migrating a whole database, rather than a subset of objects within it, or for migrating a subset of objects where you know which objects reference others.

1. Open an Explorer window for the database containing the objects that you want to migrate.
2. In the tree view, right-click the Database and select Export to WS Pro.
3. In the Select Objects For Export dialog, select the objects you want to export from the database, and any other objects referenced by them. By default all items are selected for export.

   Items with a green tick over them will be exported, items with a red cross will not. Clicking a group will toggle between these two states.

4. To prepare the selected objects for export, click OK.

   Checked out networks, and runs that depend on checked out networks, cannot be exported to the migration file. If any checked out networks are selected, a warning will be displayed and the objects will be ignored.

5. Select the export location for the file to be created (with extension .ws2wsp).

   Make sure you select a location with sufficient disk space for the complete creation of the migration file. Although migration files are compressed, the size of the migration file will depend on the specific contents of the database and the final size is difficult to predict. In particular, Oracle and SQL Server databases could easily require many gigabytes of storage when exported as a migration file.

This is the procedure for migrating a subset of objects in a database, via an intermediate JET database. This procedure assumes familiarity with JET databases.

1. Open an Explorer window for the database containing the objects that you want to migrate.

2. Either create a JET transportable database and open it or create a JET database and open it as a guest.

3. Copy objects to the JET database.

   Referenced objects will be copied across automatically.

4. Go to the root of the JET database and from the context menu select Export to WS Pro.

5. Click OK and choose the export file location.

   By default all items are selected for export.

1. Select File Open Open/Create database.

2. In the Open/Create dialog, select the type of database to create.

   Standalone databases should be used only for single-user configurations. Workgroup databases should be used whenever two or more users wish to share a database.

   For a workgroup database, specify the server name and any special connection information.

   Cloud database are for single or multi-user database stored in the cloud. This is available for Autodesk license.

3. For the type of database you have selected, click the New button:
   • For a standalone database, you will be asked to specify a location for the database to be stored by saving a .wspm file. It is important to be aware that the .wspm file does not contain the database data. The data is stored alongside the .wspm file in a folder with a long Globally Unique IDentifier (GUID) as a name. The standalone database is made up of the combination of the .wspm file and its associated folder. Note that standalone databases should always be created and stored on a local disk drive and should never be stored on a network file share.
   • For a workgroup database, you will be asked to specify the name for the new database.
   • For a cloud database, you need to select a hub from the drop-down list. If a hub is not available, you nee to create a hub and activate you subscription.

1. Open an Explorer window for the new database.
2. In the tree view, right-click the Database and select Import from migration file.
3. Browse to the migration file created earlier and click Open.

The file will be imported at the root of the database tree. Be aware that import of large data sets may take some considerable time to complete. Once the import has completed, the database can be used in InfoWorks WS Pro.

Most types of object are migrated without change in their behaviour when moving from InfoWorks WS to InfoWorks WS Pro. Some types of object are not migrated from InfoWorks WS due to major changes in the way they are represented or used in InfoWorks WS Pro.

Object types that are not migrated are:

• graphs
• themes
• workspaces

Layer lists that worked with MapX or MapObjects in InfoWorks WS will automatically be converted to work with MapXtreme or ArcGIS as appropriate, because the MapX and MapObjects map controls are no longer supported and are not available with InfoWorks WS Pro.

Note also that simulation results are not part of the migration process. Any required simulation results can be recreated by re-running the simulation after the migration is complete.