topic Re: Regarding Additional ODBC connection properties. in Qlik Replicate

Regarding Additional ODBC connection properties.

iti-attunity-sup — Tue, 26 May 2026 02:14:00 GMT

Hello Support Team,

I hope you are doing well.

We will be using the new Amazon Redshift ODBC Driver version "2.1.17".

However, UseUnicode is set to "OFF" by default, and our operational requirements mandate that UseUnicode be set to "ON".
We understand that Qlik Replicate calls the ODBC driver directly rather than using an ODBC data source (System DSN).

Therefore, we believe the UseUnicode setting needs to be configured in Manage Endpoint Connections.
Would adding UseUnicode=1 in the "Additional ODBC connection properties:" field under the Advanced settings correctly apply this configuration?

Additionally, we checked the log files to verify whether the setting has been applied, but were unable to find any message that clearly confirms it.
Could you please advise how and where we can verify that the setting has been applied correctly?
▼Reference Materials
https://docs.aws.amazon.com/redshift/latest/mgmt/odbc20-configuration-options.html#odbc20-useunicode-option
https://help.qlik.com/en-US/replicate/May2025/Content/Replicate/Main/Amazon%20Redshift/advanced_prop_redshift.htm

Best Regards.

Re: Regarding Additional ODBC connection properties.

john_wang — Tue, 26 May 2026 02:50:53 GMT

Hello @iti-attunity-sup ,

Yes, the “Additional ODBC connection properties” field in the Advanced tab of the endpoint configuration is the correct place to pass driver-level connection string parameters such as UseUnicode=1; when Qlik Replicate connects directly to the ODBC driver without using a system DSN. (please do not forget the latest semicolon)

The value you entered should be appended to the connection string that Replicate builds when opening the driver connection.

Hope this helps.

John.

Re: Regarding Additional ODBC connection properties.

iti-attunity-sup — Tue, 26 May 2026 04:13:32 GMT

Hello @john_wang ,

Thank you for your quick response.

I understand that entering UseUnicode=1 in the Additional ODBC connection properties field is the correct approach.

>The value you entered should be appended to the connection string that Replicate builds when opening >the driver connection.

Does this mean that it cannot be confirmed from the task logs?

Best Regards.

Re: Regarding Additional ODBC connection properties.

john_wang — Tue, 26 May 2026 04:22:38 GMT

Hello @iti-attunity-sup

It looks like current versions of Qlik Replicate do not print the additional ODBC connection properties in the task log. However, we can enable ODBC driver tracing to capture the detailed connection information.

Please follow the steps below:

1- Add the following values in the Redshift Target endpoint’s “Additional ODBC connection properties” field:

UseUnicode=1;LogLevel=6;LogPath=D:\\tmp\\

2- Rerun the task, then review the log file "D:\tmp\redshift_odbc.log". You should be able to find detailed connection information there, for example:

wszConnStrIn=DATABASE=qmi_rs_db;DRIVER=Amazon Redshift ODBC Driver (x64);LogLevel=6;LogPath=D:\\tmp\\;PORT=5439;PWD=****************;SERVER=qmi-johnw.myuniqueid.ap-southeast-1.redshift.amazonaws.com;SSLmode=require;UID=qmiuser;UseUnicode=1;

Hope this helps.

John.

Re: Regarding Additional ODBC connection properties.

iti-attunity-sup — Tue, 26 May 2026 05:57:03 GMT

Hello @john_wang ,

Thank you for your response.

Regarding the following statement: "when Qlik Replicate connects directly to the ODBC driver without using a system DSN. (please do not forget the latest semicolon)"

Does this phrasing imply that there is also a method that uses a system DSN?

Based on our testing, it appears that when the ODBC driver name configured in the ODBC Data Source is entered in the "odbc driver" field on the Advanced tab of the endpoint configuration, those settings are applied. Is our understanding correct?

Best Regards.

Re: Regarding Additional ODBC connection properties.

DesmondWOO — Tue, 26 May 2026 07:52:18 GMT

Hi @iti-attunity-sup ,

Configuring a 'System DSN' means you are using an ODBC target endpoint. I do not recommend this approach because ODBC is a generic solution, and architecture and syntax do not fully compatible with Amazon Redshift.

Regards,
Desmond

Re: Regarding Additional ODBC connection properties.

iti-attunity-sup — Tue, 26 May 2026 08:08:24 GMT

Hello @DesmondWOO and @john_wang

Thank you for your response.

My question was whether there is a way to reflect the Amazon Redshift ODBC Driver settings configured in the System DSN of ODBC Data Source into the Amazon Redshift endpoint settings.

However, based on your response, I understand that when using a System DSN in ODBC Data Source, we must select ODBC instead of Amazon Redshift as the target endpoint.

Could you please confirm whether our understanding is correct?

Best Regards.

Re: Regarding Additional ODBC connection properties.

john_wang — Tue, 26 May 2026 14:01:37 GMT

Hello @iti-attunity-sup ,

You are correct — we can add any ODBC settings through the endpoint’s “Additional ODBC connection properties” field.

If you use a system DSN, then the endpoint operates as a generic ODBC target endpoint. In that case, some load-specific optimizations and load capabilities may not be available.

Regards,

John.