idea Re: Qlik Replicate Postgres White Space - Status changed to: Closed - Archived in Suggest an Idea

Qlik Replicate Postgres White Space

zwatkinscovermymeds — Tue, 27 Apr 2021 14:48:05 GMT

I have noticed in Postgres there will be a column that is varchar with a character limit and Replicate will replicate that data to my sql server environment with the same character limit, but then I will get an error saying that the data has been truncated. After doing some investigating in Postgres I was able to find that the data was able to exceed the character limit. As an example the character limit on the Postgres source is 200, but I have found columns (that include white space) that have 500 characters. Is there a work around for this so that the column on the target is able to expand dynamically or is this something that can be addressed in feature request? Has anyone else run into this issue?

Re: Qlik Replicate Postgres White Space - Status changed to: Open - New

Shelley_Brennan — Tue, 01 Jun 2021 12:14:09 GMT

Have you spoken to Qlik Support about this issue yet? If so, do you have a support case we can reference? If not, I think this is the best place to start.

Re: Qlik Replicate Postgres White Space

zwatkinscovermymeds — Tue, 01 Jun 2021 18:32:51 GMT

I was advised from professional services to create an ideation ticket to see if this was an issue for anyone else in the QLIK Community before going through support. He may have an internal ticket for this issue that he created for us. To be fair, since upgrading to 7.X I have not noticed this issue, but it was a bigger problem during the implementation phase with my company. At the time we were on 6.5.

Re: Qlik Replicate Postgres White Space - Status changed to: Closed - Archived

Shelley_Brennan — Tue, 01 Jun 2021 19:28:30 GMT

Ah - I would recommend posting on the Replicate user forum - you may get more feedback in that area of Qlik Community. https://community.qlik.com/t5/Qlik-Replicate/bd-p/qlik-replicate-discussions

If you do encounter this issue on version 7.x I would recommend opening a ticket with Qlik Support and get their feedback. If we need to re-open this post we can.

Thank you!