SnowFlake target latency due to connectivity issues

[OritA]

When SnowFlake target latency is caused by SnowFlake connectivity issues, the following configuration settings should be performed:  

1. Change the setting of SnowFlake connection string:
   1. Stop the task
   2. Go to Snowfalke endpoint target, under the advanced tab, additional ODBC connection string and set the following parameters:
      CLIENT_SESSION_KEEP_ALIVE=true;ABORT_DETACHED_QUERY=true;CLIENT_SESSION_KEEP_ALIVE_HEARTBEAT_FREQUENCY=900;

Further details on these parameters can be found on SnowFlake documentation under the following link: https://docs.snowflake.com/en/index.html

2. On the Replication Server machine, add the following registry keys:

HKEY_LOCAL_MACHINE/SOFTWARE/Snowflake/Driver/CLIENT_SESSION_KEEP_ALIVE value=true
HKEY_LOCAL_MACHINE/SOFTWARE/Snowflake/Driver/CLIENT_SESSION_KEEP_ALIVE_HEARTBEAT_FREQUENCY value=900
HKEY_LOCAL_MACHINE/SOFTWARE/Snowflake/Driver/ABORT_DETACHED_QUERY value=true

3. For the Snowfalke user used by Replicate, perform the following settings:
   alter user user_name set CLIENT_SESSION_KEEP_ALIVE = TRUE;
   alter user user_name set ABORT_DETACHED_QUERY = TRUE;
   alter user user_name set CLIENT_SESSION_KEEP_ALIVE_HEARTBEAT_FREQUENCY = 900;

Further details on the above setting can be found in the SnowFlake documentation under the following link:https://docs.snowflake.net/manuals/sql-reference/parameters.html#client-session-keep-alive

4. Resume the task

Environment

• Qlik Replicate replicating to SnowFlake target endpoint