Following Spotfire 5.0, it has been possible to push data calculations and aggregations to the source system, facilitating the handling of data volumes too large to fit into the primary memory and take advantage of the power of the source database. When using this in-database (in-db) analytic functionality, you access only a selected or aggregated set of data.

When a visualization is configured to use an in-db connection, every time a change is made to the visualization's data-dependent properties, a new query is sent to the external data source and a new table of aggregated data is returned.

The use of in-db data, as opposed to in-memory data, does introduce limitations. For example, automatic date and time hierarchies are not available. Consult the in-line help on working with in-database data for a full list of constraints.

So, how do you use in-db analytics? You start by adding a data connection, as distinct from a data...