Storing assets within STEP can greatly increase the database size. As the database grows, the time required to back up the database also grows. Deleting assets from STEP does not automatically recalculate the database size; this means the time required to back up the database is not reduced. Updating the database size after asset deletion requires that the database be compressed and then restored. An effective way to avoid this whole scenario is to store assets outside of STEP, while continuing to allow them to be displayed in and exported from STEP.
Important: Assets stored outside of STEP are not supported by Stibo Systems. Storing assets externally increases your responsibility for managing the assets, as well as the management and maintenance of the selected external system.
Details about the options for storing assets externally are defined in the following sections:
- External Digital Asset Management (DAM) (here) - where a URL is used to retrieve the asset content
- External File Structure (EFS) (here) - where a unique file name is used to retrieve the asset content
For both of these methods, configuration asset files (such as transformation lookup tables and export configurations) will be stored within STEP.
Regardless of the method used to store assets, either in STEP or externally, assets must be linked into at least one classification, can be referenced by products and entities, can be approved, and can be imported and exported. For more information about using assets within STEP, refer to the Digital Assets topic here.