Limitations and considerations

The following limitations apply when using the Snowflake on Azure target endpoint in a Replicate task:

• Replication of tables with backslashes in their names (for example, SPECIAL\\TABLE\N) is not supported.
• When Bulk Loading is set as the loading method, the Transactional apply Change Processing mode is not supported.
• When using Snowpipe Streaming as the loading method, the following limitations apply:
  • As Snowpipe only supports INSERT operations, the Apply Changes replication option will not be available.
  • When the Store Changes replication option is enabled, changes can only be stored in Change tables, not in an Audit table.
  • The Batch optimized apply change processing mode is not supported.
  • Username and password authentication is not supported.
  • OAuth authentication is not supported.
  • The XML subtype is not supported.
  • The Snowflake SDK uses a static HTTP client, which is shared among all Snowpipe clients in the JVM/process. In practice, this means that after performing the initial Test Connection for a Snowflake endpoint configured with proxy settings, all subsequent Test Connections will use the initial proxy settings, even if they were later modified or the proxy was enabled/disabled. So, for example, if you change the proxy host after performing a Test Connection, any subsequent Test Connections you perform will continue to use the original host name.
  • For character data types that contain NULLs within the string, Replicate sends the data until the first NULL.
  • Stopping Store Changes replication during a transaction and resuming it after 30 days or more might cause duplicate records on target. Snowflake automatically deletes channels after 30 days.
  • Replicating data with 4-byte emoji characters is not supported.