Skip to main content

Instances and Settings

This article describes the settings available for instances in Jet Analytics Data Integration. Instances are the building blocks of a Jet Analytics Data Integration solution — a solution is composed of three types: Ingest, Prepare, and Deliver instances.

To access instance settings, right-click an instance and select Edit Instance.

Ingest instance settings

The Ingest instance settings display information from the instance configuration in the Jet Analytics Portal. The information shown depends on the storage type selected for the instance.

Prepare instance settings

The Prepare instance settings display information from the instance configuration in the Jet Analytics Portal. The default settings and options are described below.

  • Postfix valid tables: When set to Yes, the _V postfix is added to valid table names. The default is No.
  • Type for new relations: Controls how Jet Analytics Data Integration handles foreign key violations. The default is Relation.
    • Error — moves the offending row to the error table.
    • Warning — moves the offending row to the warning table.
    • Physical — ignores the violation.
  • Index generation: Sets the default index generation behaviour.
    • Automatic — indexes are created automatically as needed.
    • Manual — automatic index generation is enabled on a per-table basis.
    • Disabled — no indexes are created automatically.
  • Primary key behaviour: Controls how Jet Analytics Data Integration handles primary key violations. The default is Error.
    • Error — moves the offending row to the error table.
    • Warning — moves the offending row to the warning table.
    • None — ignores the violation.
  • Allow null values: When set to Yes (default), fields are permitted to contain null values. When set to No, any rows with null field values are moved to the error table.
  • Null check approach:
    • Field Based (default) — identifies both the record and the specific field that contains the null value.
    • Record Based — identifies only the record that contains a null value, without referencing the specific field.
  • Hashing algorithm: Selects the algorithm used for hash fields. See Hashing algorithms below for descriptions of each option.

Hashing algorithms

  • SHA-2 512, SQL Server 2016+: The most collision-resistant algorithm available. Produces a 64-byte hash. Approximately 40% slower than SHA-1, SQL Server 2016+, and should only be used when maximum hash safety is required. Requires SQL Server 2016 or later.
  • SHA-1, SQL Server 2016+: The fastest algorithm when the data to be hashed exceeds 8,000 bytes — approximately 30% faster than SHA-1, SQL Server 2005+ in those cases. Performance is otherwise comparable. Produces a 20-byte hash. Requires SQL Server 2016 or later.
  • SHA-1, SQL Server 2005+: The default algorithm. Produces a 20-byte hash and is compatible with all SQL Server versions supported by Jet Analytics Data Integration. Slower than SHA-1, SQL Server 2016+ when hashing more than 8,000 bytes of data.
  • Plain text (debug): For debugging only. Concatenates the fields into a string to make the hash input visible. Limited to 4,000 characters due to a SQL Server constraint.
  • Legacy binary: Included for compatibility with earlier versions of Jet Analytics Data Integration. Not type-safe and limited to 4,000 characters across all fields used in the hash. Do not use in new instances.
  • Legacy plain text (debug): For debugging legacy algorithms. Concatenates the fields into a string up to 4,000 characters.

Deliver instance settings

The Deliver instance settings display information from the instance configuration in the Jet Analytics Portal. The information shown depends on the selected endpoint type. The Hashing algorithm options are identical to those described for the Prepare instance above.

Was this article helpful?

We're sorry to hear that.