(Glue-2411) SNP Glue Table Consumer

Owned by SNP
yesterday at 10:41 am
3 min read

SNP Glue Table Consumer uses the SNP Glue table as a target for data. 

Creation of the SNP Glue Table Consumer

Perform the steps outlined in How to Create a Consumer Object with the option SNP Glue Table Consumer selected under the Component implementation dropdown of step 4.

Activation of the SNP Glue Table Consumer

After creation, the object is in the saved state. For activation, all mandatory inputs need to be filled in.

  • SNP Glue Table
    • Name of the SNP Glue table as a target for data
    • Provided with F4 help
  • Enable merge
    • The flag that will enable the merge operation
    • It can also be enabled/disabled in the Extraction process selection screen

Please note that SNP plans to decommission the Enable Merge feature in the SNP Glue extraction process. Starting with release 2502, this feature will no longer be configurable and will be fully removed in release 2511. 

The Enable Merge feature was originally introduced to perform delta updates on connected data storage. However, its direct integration with the load process has proven to be inefficient. We now offer more efficient methods for performing merges by decoupling the load and merge processes, utilizing platform-based solutions such as our native app. This approach not only improves performance but also reduces credit consumption.

As a result, we have decided to transition to these improved functionalities and decommission the Enable Merge feature. This change affects only Enable Merge and does not impact the Enable Update feature or customers replicating to SQL databases.

  • Keep deleted entries
    • This flag will keep deleted entries in the target table while using merge functionality.
    • Enable merge must be allowed.
    • If field GLREQUEST is present, this field must be not a key field.
  • Deletion flag fieldname
    • Only visible when the Enable merge checkbox is checked
    • Name of the field that flags if the record was deleted
    • Must exist in the SNP Glue table (can be added using the  button in the Import fields screen).
  • Merge timestamp
    • Also visible only when the merge is enabled
    • Name of the field that distinguishes when the record was inserted in the table
    • Must exist in the SNP Glue table (can be added using the  button in the Import fields screen).


It is possible to adjust the SNP Glue Table consumer's structure automatically when it is combined with Advanced DSO in the Extraction Process. For more information, see the chapter (Glue-2411) Automatic adjustment of Consumer structure. 

Transparent storages with secondary DB

No deletion flag is required for transparent storages with a secondary DB connection. However, keeping deleted entries is also not supported.

Merge in secondary DB connection storage is handling simple operations (INSERT, UPDATE, DELETE) that are not advanced, for example, INSERT → UPDATE.

Connection to storage failed

When connection to storage failed and merge was enabled, there is a possibility to force delete merge metadata after deactivating a consumer.