Preference Group/Preference |
Description |
DataOptimizationPreferences |
|
AllowSavingOnDemandData |
Determines whether on-demand data should be allowed to be stored in an analysis. Default is True. Change to False to make sure no on-demand data can be stored. The column names will always be stored in the analysis, as in all cases of linked data, even when the preference is set to False. Note: If the on-demand source is the only data source and the data table is embedded at the top level, then this setting will not have any effect. |
DisableAutomaticOnDemandInEmbeddedTables |
Allows you to completely disable automatic on-demand loading in data tables that are top-level embedded. |
DropVisualizationMemoryWhenSwitchingPages32 |
Determines whether to drop visualization views from memory when switching page, when running in 32-bit mode. Default is False. |
DropVisualizationMemoryWhenSwitchingPages64 |
Determines whether to drop visualization views from memory when switching page, when running in 64-bit mode. Default is False. |
ExportSbdfWithRunLengthEncoding |
Determines whether to use Run Length Encoding (RLE) when exporting data files in SBDF format (Spotfire Binary Data Format file). Enabling RLE might lead to better performance for the file export and import because RLE encoded files are often smaller and are therefore transmitted faster. Default is True. |
LegacyReloadData |
This is an advanced preference that should not be changed unless you are explicitly instructed to do so by a Spotfire support engineer. Default is False. |
MarkingInQueryLimit |
Limit applicable for queries within a single column. Specifies the limit for how large queries should be allowed when marking or transferring markings or filterings between related tables. If the limit is exceeded when working with in-database data, then no marking or filtering will take place. Default is 15000. Note: Some connectors (e.g., for connections to Oracle) have a built-in limit that cannot be changed. |
MarkingWhereClauseLimit |
Limit applicable for queries involving multiple columns. Specifies the limit for how large queries should be allowed when marking or transferring markings or filterings between related tables. If the limit is exceeded when working with in-database data, then no marking or filtering will take place. Default is 1000. Note: Some connectors (e.g., for connections to Oracle) have a built-in limit that cannot be changed. |
MaxCrossHierarchyLeafNodeCount |
Limit for leaf node size for cross hierarchies. This limit can prevent users from accidentally creating huge tables using cross join. Default is 10000000. |
MaxMissingTimeParts |
A limit used when compensating for missing values, determining the max number of rows that can be inserted. If the range of the date/time column is significantly larger than the step size, a huge number of rows may be needed to compensate for missing values. Modifying this limit can affect the performance of missing value-compensated visualizations. |
ReloadDataAsynchronously |
[Only applicable if LegacyReloadData is set to True.] Determines whether to reload data asynchronously. The Default is True. |
ShowFilteredByOthers |
Lets you disable the ”filtered by others”-functionality for filters on the web clients or in the text area, currently only applicable to the hierarchy filter. This can decrease the rendering time when showing the filter, because the calculation to determine which values have been filtered out using the other filters is skipped. |
UseSpecialPivotWhenApplicable |
Specifies whether to use the special pivot mechanism (when this is applicable). The special pivot is developed to improve performance for some special use cases when the only aggregations used are Max, Min, First and None, and the memory is limited. For all other cases then this pivot method should not be used. The Default is False. |
See also: