.Stat Suite documentation

.Stat CORE configuration

Table of Content

SQL Server configuration without SQL Mgmt Studio

The Database Configuration Tool can be used for the configuration of MS SQL server databases in situations where those databases cannot be accessed directly, e.g. in containerised installation approaches, or in environments like the SIS-CC DevOps one.

It currently supports the following tasks:

  • Set database recovery mode set to SIMPLE (always executed)
  • Adjust maximum size of Data & Log files (optional)

Detailed information can be found here.

.Stat Suite data space compression

Introduced in August 24, 2023 Release .Stat Suite .NET ’elote’

The Transfer web service configuration setting Archive (boolean, default false) controls the compression behaviour of a data space. If set to true then all the data and referential metadata stored in the concerned data space are considered archived (almost static) and the related database tables use an SQL COLUMNSTORE_ARCHIVE data compression.

All the existing Transfer and SDMX (NSI) API functionality remains for Archived dataspaces.

A dataspace can already contain data and be configured later as Archived. In this case after a init/dataflow, transfer or import, the data/referential metadata will be compressed.

Once the data and referential metadata is Archived, there is no implementation to remove the table compression again. In other words, if a data space configured as Archived is reconfigured to non Archived, the previously contained Archived data and refrerential metadata will continue to be compressed.

Archived data spaces do not use unique constraints to garantee unique observations. This is achieved instead by validating duplicates while importing/transfering data and referential metadata.

When data is imported, it is automatically compressed. This can cause increased CPU usage compared to non-Archived data spaces. When data is exported, it is automatically uncompressed again.

Compression does not affect backup, restore nor log shipping.

Benefits and costs:

  • Compressing columnstore indexes with archival compression, causes the index to perform slower than columnstore indexes that do not have the archival compression. Use archival compression only when you can afford to use extra time and CPU resources to compress and retrieve the data.
  • The benefit of archival compression, is reduced storage, which is useful for data that is not accessed frequently. For example, if you have a partition for each month of data, and most of your activity is for the most recent months, you could archive older months to reduce the storage requirements. The estimated compression rate (depending on the data content) is at least 80%.

For more information, see here.