Any referenced datasets can be downloaded from "Module downloads" in the module overview.
Transcript
00:03
In WS Pro, all modelling data is saved into a database.
00:08
The database is either a standalone, workgroup, or cloud database.
00:13
Result files are associated to the database files, but they are stored separately.
00:19
A standalone database is saved as a .wspm file and has an associated unique identifier folder.
00:26
The folder will contain all of the database information.
00:31
The .wspm file and associated folder must be kept together.
00:36
The standalone database is designed for a single user and should not be saved on a network drive or file share.
00:43
A workgroup database is saved as a .sndb folder.
00:48
The folder will contain all of the database information.
00:52
The workgroup databases are managed via the Workgroup Data Server service,
00:57
which is installed separately.
00:59
This can be run locally to manage an individual's databases
01:03
or from a centralized location to enable multi-user access.
01:08
The 2024 release of WS Pro introduced cloud databases,
01:12
which allow users to store and manage project data in the cloud.
01:16
Using an integrated cloud database manager, administrators can back up and recover model data
01:22
from an accessible web-based environment.
01:24
In this view, admins can review databases that their team are working on, as well as the date a backup was created for each version.
01:32
They can manually create new backups, restore from an existing backup, or delete a database that is no longer needed.
01:40
Regardless of which type of database is in use, you can transfer data using a transportable database file.
01:47
A new transportable database is created from the file menu within the user interface.
01:52
Data is then copied into the transportable file.
01:56
Upon closing, it is compressed into a single .wspt file and can be shared externally.
02:03
When creating a transportable database, you can select which database version should be created.
02:09
This is important to ensure that the person receiving the data is able to open it.
02:14
Note that you cannot copy data from a newer version into an older transportable database.
02:20
The option will not be available.
02:23
Many of the files used in these examples are stored in transportable databases.
02:28
Open .wspt files from the File menu and copy the contents into your database.
02:34
As an individual or group of users, you can have as many or few databases as you desire.
02:40
There is no size limit to a database, although excessively large databases may suffer in performance and be cumbersome to navigate.
02:48
Best practice is to plan how to structure your databases around your projects to manage access and resources.
02:54
It is recommended that all users utilize the workgroup database over the standalone.
00:03
In WS Pro, all modelling data is saved into a database.
00:08
The database is either a standalone, workgroup, or cloud database.
00:13
Result files are associated to the database files, but they are stored separately.
00:19
A standalone database is saved as a .wspm file and has an associated unique identifier folder.
00:26
The folder will contain all of the database information.
00:31
The .wspm file and associated folder must be kept together.
00:36
The standalone database is designed for a single user and should not be saved on a network drive or file share.
00:43
A workgroup database is saved as a .sndb folder.
00:48
The folder will contain all of the database information.
00:52
The workgroup databases are managed via the Workgroup Data Server service,
00:57
which is installed separately.
00:59
This can be run locally to manage an individual's databases
01:03
or from a centralized location to enable multi-user access.
01:08
The 2024 release of WS Pro introduced cloud databases,
01:12
which allow users to store and manage project data in the cloud.
01:16
Using an integrated cloud database manager, administrators can back up and recover model data
01:22
from an accessible web-based environment.
01:24
In this view, admins can review databases that their team are working on, as well as the date a backup was created for each version.
01:32
They can manually create new backups, restore from an existing backup, or delete a database that is no longer needed.
01:40
Regardless of which type of database is in use, you can transfer data using a transportable database file.
01:47
A new transportable database is created from the file menu within the user interface.
01:52
Data is then copied into the transportable file.
01:56
Upon closing, it is compressed into a single .wspt file and can be shared externally.
02:03
When creating a transportable database, you can select which database version should be created.
02:09
This is important to ensure that the person receiving the data is able to open it.
02:14
Note that you cannot copy data from a newer version into an older transportable database.
02:20
The option will not be available.
02:23
Many of the files used in these examples are stored in transportable databases.
02:28
Open .wspt files from the File menu and copy the contents into your database.
02:34
As an individual or group of users, you can have as many or few databases as you desire.
02:40
There is no size limit to a database, although excessively large databases may suffer in performance and be cumbersome to navigate.
02:48
Best practice is to plan how to structure your databases around your projects to manage access and resources.
02:54
It is recommended that all users utilize the workgroup database over the standalone.
Required for course completion
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.
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.
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.
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:
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.
Many files used in these examples are stored in transportable databases.
Open .wspt files from File menu, then copy contents into database.
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.
