https://community.qlik.com/t5/Suggest-an-Idea/Column-Collation-Not-Replicated-with-Parallel-Load/idi-p/1773883 <P>Hello,</P> <P>On Microsoft Sql Server, our source database collation is SQL_Latin1_General_CP1_CI_AS however we have column collations that are SQL_Latin1_General_CP1_CS_AS. If we define the replicate task without any transformations, it maintains this column collation. However if we add transformations, the column collation changes to SQL_Latin1_General_CP1_CI_AS.</P> <P>I can understand this limitation when the table is manipulated, either transformations to existing columns or adding columns that subsequently change the table definition. Unfortunately this issue also occurs when we select a table for parallel load. As we have some larger source tables requiring the case sensitive collation, it would help our full load if we could utilize the parallel load.</P> <P>We submitted a case support asking about this issue and it was determined this limitation was by design, however this wasn't clearly indicated in the documentation (p. 284 of the handbook&nbsp;<A href="https://help.qlik.com/en-US/replicate/November2020/pdf/Replicate%20Setup%20and%20User%20Guide.pdf" target="_blank" rel="noopener">https://help.qlik.com/en-US/replicate/November2020/pdf/Replicate%20Setup%20and%20User%20Guide.pdf</A>&nbsp;says "When replicating from one Microsoft SQL Server database to another, column and table collations will be&nbsp;replicated to the target. ")</P> <P>Thank you!</P> Wed, 27 Jan 2021 21:45:39 GMT Anonymous 2021-01-27T21:45:39Z https://community.qlik.com/t5/Suggest-an-Idea/Column-Collation-Not-Replicated-with-Parallel-Load/idi-p/1773883 <P>Hello,</P> <P>On Microsoft Sql Server, our source database collation is SQL_Latin1_General_CP1_CI_AS however we have column collations that are SQL_Latin1_General_CP1_CS_AS. If we define the replicate task without any transformations, it maintains this column collation. However if we add transformations, the column collation changes to SQL_Latin1_General_CP1_CI_AS.</P> <P>I can understand this limitation when the table is manipulated, either transformations to existing columns or adding columns that subsequently change the table definition. Unfortunately this issue also occurs when we select a table for parallel load. As we have some larger source tables requiring the case sensitive collation, it would help our full load if we could utilize the parallel load.</P> <P>We submitted a case support asking about this issue and it was determined this limitation was by design, however this wasn't clearly indicated in the documentation (p. 284 of the handbook&nbsp;<A href="https://help.qlik.com/en-US/replicate/November2020/pdf/Replicate%20Setup%20and%20User%20Guide.pdf" target="_blank" rel="noopener">https://help.qlik.com/en-US/replicate/November2020/pdf/Replicate%20Setup%20and%20User%20Guide.pdf</A>&nbsp;says "When replicating from one Microsoft SQL Server database to another, column and table collations will be&nbsp;replicated to the target. ")</P> <P>Thank you!</P> Wed, 27 Jan 2021 21:45:39 GMT https://community.qlik.com/t5/Suggest-an-Idea/Column-Collation-Not-Replicated-with-Parallel-Load/idi-p/1773883 Anonymous 2021-01-27T21:45:39Z https://community.qlik.com/t5/Suggest-an-Idea/Column-Collation-Not-Replicated-with-Parallel-Load/idc-p/1777147#M4820 <P>Could you share the support case number with us?&nbsp; Thank you!</P> Mon, 25 Jan 2021 14:19:53 GMT https://community.qlik.com/t5/Suggest-an-Idea/Column-Collation-Not-Replicated-with-Parallel-Load/idc-p/1777147#M4820 Shelley_Brennan 2021-01-25T14:19:53Z https://community.qlik.com/t5/Suggest-an-Idea/Column-Collation-Not-Replicated-with-Parallel-Load/idc-p/1777177#M4822 Hello,<BR />Thank you for your help with this issue. The case number we submitted is: 02088020<BR />Thank you!<BR /> Mon, 25 Jan 2021 15:12:44 GMT https://community.qlik.com/t5/Suggest-an-Idea/Column-Collation-Not-Replicated-with-Parallel-Load/idc-p/1777177#M4822 Anonymous 2021-01-25T15:12:44Z https://community.qlik.com/t5/Suggest-an-Idea/Column-Collation-Not-Replicated-with-Parallel-Load/idc-p/1779518#M4897 <P>We are still looking into this on our side and hope to have another update for you soon.&nbsp; Thanks!</P> Tue, 02 Feb 2021 20:58:49 GMT https://community.qlik.com/t5/Suggest-an-Idea/Column-Collation-Not-Replicated-with-Parallel-Load/idc-p/1779518#M4897 Shelley_Brennan 2021-02-02T20:58:49Z https://community.qlik.com/t5/Suggest-an-Idea/Column-Collation-Not-Replicated-with-Parallel-Load/idc-p/1780901#M4948 <P>We have analyzed this further and determined that this is indeed a bug.&nbsp; We have reopened your support case&nbsp;<SPAN>02088020 to handle this.&nbsp; Thanks for your patience!</SPAN></P> Mon, 08 Feb 2021 14:50:00 GMT https://community.qlik.com/t5/Suggest-an-Idea/Column-Collation-Not-Replicated-with-Parallel-Load/idc-p/1780901#M4948 Shelley_Brennan 2021-02-08T14:50:00Z