Storing and sharing InfoWorks WS Pro data
As an administrator, you will understand how WS Pro data is stored and shared.
Storing and sharing InfoWorks WS Pro data
Understand how WS Pro data is stored and shared.
In WS Pro, all modelling data is saved into a database.
The database is either a standalone, workgroup, or cloud database.
Result files are associated to database files, but stored separately.
Standalone Database:
Saved as .wspm file with associated unique identifier folder containing all database information—.wspm file and associated folder must be kept together.
Designed for single user and should not be saved on network drive or file share.
Workgroup Database:
Saved as .sndb folder containing all database information.
Managed via Workgroup Data Server service, installed separately.
Workgroup Data Server can be run locally to manage individual's databases, or from centralized location to enable multi-user access.
Cloud Database:
Introduced in WS Pro 2024.
Allows users to store and manage project data in the cloud.
Using integrated cloud database manager, administrators can back up and recover model data from accessible web-based environment.
In this view, admins can:
- review team databases
- view date of backup creation for each version
- manually create new backups
- restore from existing backup
- delete a database
Transportable Database:
Used to transfer data, regardless of database type.
Create from File menu within user interface, then copy data into transportable file.
Upon closing, data is compressed into single .wspt file that can be shared externally.
Can select which database version should be created—important to ensure person receiving data can open it.
Note that data cannot be copied from newer version into older transportable database.
Tutorial Example Files:
Many files used in these examples are stored in transportable databases.
Open .wspt files from File menu, then copy contents into database.
Recommendations:
An individual or group of users can have as many or as few databases as desired.
No size limit to database, although excessively large databases may suffer in performance and be cumbersome to navigate.
Best practice is to plan how to structure databases around projects to manage access and resources.
It is recommended that all users utilize workgroup database over standalone.