Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content
Announcements
UPGRADE ADVISORY for Qlik Replicate 2024.5: Read More
cancel
Showing results for 
Search instead for 
Did you mean: 
NakulanR
Partner - Creator
Partner - Creator

Licensing implications of the new unified Snowflake target endpoint

Hi Support,

 

In the What's New section of the user guide for the upcoming May 2025 release of Replicate (here), there's a part which talks about unifying the Snowflake target endpoints into a single endpoint rather than having a separate one for each cloud provider.

The note says that by the November 2025 release, all the standalone endpoints will be merged into the single unified endpoint using the existing license. (see below)

NakulanR_0-1745974091966.png

What does that mean from a licensing standpoint? Considering current replicate licenses list the Snowflake targets with the cloud providers (example below). Does this mean that customers using Snowflake as a target will need a new license where the target_type would be 'Snowflake'? Or would they be able to continue with the license they have, and Replicate will detect that 'SnowflakeAWS', for example, is a valid target_type to have in the license?

NakulanR_1-1745974178403.png

 

Any insight into this is greatly appreciated.

 

Thanks,

Nak

 

 

1 Solution

Accepted Solutions
john_wang
Support
Support

Hello Nak, @NakulanR 

Qlik Replicate 2025.5 behaves as follows:

1. After upgrading to Replicate 2025.5 , existing standalone Snowflake target endpoints remain unchanged. It will NOT automatically merged into new EP "Snowflake".

    This behavior will be changed in Replicate 2025.11Upgrading to Replicate November 2025 will automatically merge any standalone Snowflake target endpoints into the new unified Snowflake target endpoint, using your existing license.

2. The license token must match the standalone Snowflake target type , otherwise, tasks will not run in Replicate 2025.5. As same as in previous old versions.

3. The new unified Snowflake endpoint is compatible with the three existing standalone Snowflake license tokens, as well as with the new license token "target_types=Snowflake".

Regarding the questions:

>> Does this mean that customers using Snowflake as a target will need a new license where the target_type would be 'Snowflake'?

Not necessarily.

>> Or would they be able to continue with the license they have, and Replicate will detect that 'SnowflakeAWS', for example, is a valid target_type to have in the license?

Yes, it would honor old tokens.

Hope this helps.

John.

Help users find answers! Do not forget to mark a solution that worked for you! If already marked, give it a thumbs up!

View solution in original post

2 Replies
john_wang
Support
Support

Hello Nak, @NakulanR 

Thank you so much for opening the article - this is an excellent question. I'm really glad to see you're keeping up with the 2025.5 TP release.

Please give me a few minutes to confirm the behavior. I'll get back to you shortly with my findings.

Regards,

John.

 

 
Help users find answers! Do not forget to mark a solution that worked for you! If already marked, give it a thumbs up!
john_wang
Support
Support

Hello Nak, @NakulanR 

Qlik Replicate 2025.5 behaves as follows:

1. After upgrading to Replicate 2025.5 , existing standalone Snowflake target endpoints remain unchanged. It will NOT automatically merged into new EP "Snowflake".

    This behavior will be changed in Replicate 2025.11Upgrading to Replicate November 2025 will automatically merge any standalone Snowflake target endpoints into the new unified Snowflake target endpoint, using your existing license.

2. The license token must match the standalone Snowflake target type , otherwise, tasks will not run in Replicate 2025.5. As same as in previous old versions.

3. The new unified Snowflake endpoint is compatible with the three existing standalone Snowflake license tokens, as well as with the new license token "target_types=Snowflake".

Regarding the questions:

>> Does this mean that customers using Snowflake as a target will need a new license where the target_type would be 'Snowflake'?

Not necessarily.

>> Or would they be able to continue with the license they have, and Replicate will detect that 'SnowflakeAWS', for example, is a valid target_type to have in the license?

Yes, it would honor old tokens.

Hope this helps.

John.

Help users find answers! Do not forget to mark a solution that worked for you! If already marked, give it a thumbs up!