Library content storage outside of the Spotfire database
To minimize the size of your Spotfire database, you can store your organization's Spotfire library content (analyses and analysis data) in the cloud using different solutions, or in a file system elsewhere.
In a typical
Spotfire
installation, the largest part of database storage consists of the library
content. When you move the library content to external storage, only the
metadata about the library files remains in the database. The other items in
database storage (system configuration data, permissions, licenses, and so on)
remain where they are.
Note: In this scenario,
all library content is stored externally; it is not possible to
split storage between the server database and the external site.
Currently there are three main drawbacks to this option:
- Referential integrity is not guaranteed; there is the possibility that content referenced in the Spotfire database will not exist in external storage, and vice versa.
- Your system may run more slowly, such as when loading files.
- A database backup will not back up the library content.
- Configuring external library storage in AWS
You can configure external library storage in the cloud using Amazon Web Services S3 (AWS). - Configuring external library storage in Azure Blob Storage
You can configure external library storage in the cloud using Azure Blob Storage. - Configuring external library storage in a file system
You can configure external library storage in a file system by using the command line. - Monitoring external library storage and fixing inconsistencies
Because there is no guarantee of referential integrity when using external library storage, the administrator should regularly check for inconsistencies between the metadata in the Spotfire database and the files in external storage.
Parent topic: Command-based library administration tasks
Related reference