This topic describes the locations where cloud or on-premise database and transitory data are stored when using InfoWorks ICM.
Cloud and on-premise Databases
- Standard
- Oracle
- SQL Server
Standard
When you create the on-premise database, you can choose the location of the database index (ICMM) file that forms the entry point to the database.
The files containing the database data are stored in a sub-folder of this location. The name of the sub-folder is the Unique Database Identifier for the database. If you have more than one database in the same folder, there will be a sub-folder for each database.
Oracle
The location of the on-premise database is controlled by the database server and you cannot change this location.
Any additional files are stored in sub-folders of the Remote Root folders. The name of the sub-folder of each remote root is the Unique Database Identifier for the database. If you have more than one database there will be a sub-folder for each database.
The location of the Remote Root folders is independent of the location of the database.
SQL Server
The location of the on-premise database is controlled by the database server and you cannot change this location.
Any additional files are stored in sub-directories of the Remote Root directories. The name of the sub-folder of each remote root is the Unique Database Identifier for the database. If you have more than one database there will be a sub-folder for each database.
The location of the Remote Root directories is independent of the location of the database.
Remote roots
The following additional files may be found in the Remote Root folders for on-premise databases:
Remote Root |
Files Stored in Remote Root |
||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Remote Results Root |
Results files of InfoWorks ICM simulations run on the server or moved to the server are stored in the Remote Results Root:
Cached trace results files are available if the agent running the on-premise simulation has been configured to generate these type of files. If available, these will be used for retrieving results trace data for graphs and statistical reports instead of the simulation results files listed above.
State Files: these snapshot files can be created at a specified date-time during a simulation and used as the initial state for additional simulations; a method commonly used for water quality modelling.
|
||||||||||||||||||||||||||||||||||||||||
Remote Files Root |
If GIS Layer files and hyperlinked files are stored in the Remote Files Root, Layer List and Hyperlink paths will be saved relative to the Remote File Root. |
Local folders
Each on-premise and cloud database has a sub-folder of the local working folder containing transitory data and the local results folder containing local results files. The name of the sub-folder is the Unique Database Identifier for on-premise databases and the Unique Identifier for the cloud database. If using more than one database, there will be a sub-folder for each database.
The local working folder contains:
- Working copies of networks
- Other temporary working files
The local results folder contains:
File types | Description | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Results files |
These are locally stored on-premise or cloud results files. For on-premise databases, you can choose to place results on the server or keep them locally when scheduling a simulation. You can also use the Results Management facilities to move results to the server later. For cloud databases, you choose whether or not to download the results to your local results folder when scheduling a simulation. Results, that are not available locally, can be downloaded from the cloud.
|
||||||||||||||||
Cached trace results files |
These files are available if the agent running an on-premise simulation has been configured to generate them. If available, these will be used for retrieving results trace data for graphs and statistical reports instead of the simulation results files listed above.
|
||||||||||||||||
State files |
These are snapshot files for cloud databases that are created at a specified date-time during a simulation and used as the initial state for additional simulations. This is a method commonly used for water quality modelling. Note: For
on-premise databases, state files are stored in the Remote Root folders.
|
||||||||||||||||
Other files |
Temporary files used for setting up simulations. Sometimes, these files are not cleared up properly, for example if the simulation fails or is stopped part way through. To clean up these temporary files you should use the facilities provided within InfoWorks ICM. See Local Folders. |
Filenames
All filenames follow the same pattern.
- The letters at the start of the filename identify the type of object in the file. The letters are:
- NET - network
- SIM - simulation
- The number following the letters is the internal identifier for the object in the database. You can see this identifier when you right-click on an object in the Explorer Window and choose Properties from the popup menu. The identifier is shown in the ID field.
- The suffix will probably be one of those in the list above. If not, the file is a temporary file that has not been deleted.