Skip to content

Prerequisites

It is important to understand not all valid kdb+ databases are suitable for the initial import process. A database can only be imported automatically with minimal overhead if it meets the following prerequisites:

  • Partitioned tables must be partitioned by date in the standard format for a partitioned (non-segmented) database. kdb+ Insights does not support partitioning by month, year or integer in the historical tiers.
  • Partitioned tables must have a 'partition column': a timestamp column which, when rounded down, is equal to the date column. Read the documentation on the prtnCol field in schema definitions.
  • Encrypted databases must use the same encryption settings and encryption key in kdb+ Insights as before import. Read the 'Encryption' section for details.
  • Compressed databases should also use the same compression settings. In addition, compression settings must be the same for all tables.
  • The database must have a single enumeration file named sym.
  • The entire database must be able to fit into the first HDB storage tier. If it is larger, it may be possible to import as much data as possible into the first tier and then batch ingest the remaining partitions.
  • The must be no overlap between partition values across tiers.
  • Non-partitioned tables should exist in the local database root.
  • Ensure a backup copy of the data exists.

Backup policy

The backup is not enforced, since it is likely originating in a different volume before being copied to the SM volume. You must ensure that this data is backed up somewhere prior to starting SM.

If your database does not meet all of the above prerequisites, it may not be suitable for initial import without modification.

Next steps

Once the prerequisites are fulfilled, you can move on to the following guides: