<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Replication of MS SQL Server table with Columnstore Index in Qlik Replicate</title>
    <link>https://community.qlik.com/t5/Qlik-Replicate/Replication-of-MS-SQL-Server-table-with-Columnstore-Index/m-p/2010837#M4369</link>
    <description>&lt;P&gt;Hello &lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/165296"&gt;@jmiao&lt;/a&gt; ,&lt;/P&gt;
&lt;P&gt;Replicate provides 2 drivers to capture Microsoft SQL Server source DB changes. One way is reading changes from TLOG, another approach is using MS-CDC. However both of the drivers cannot get changes from &lt;SPAN&gt;table with Columnstore Index, this is because of Microsoft SQL Server itself limitation rather than Replicate limitation.  Here is the MS docs reference page &lt;A title="Columnstore indexes can't be combined with the following features" href="https://learn.microsoft.com/en-us/sql/t-sql/statements/create-columnstore-index-transact-sql?view=sql-server-ver15" target="_blank" rel="noopener"&gt;Columnstore indexes can't be combined with the following features&lt;/A&gt; .&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Totally agree with &lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/113691"&gt;@lyka&lt;/a&gt; , I think this is the one option (without change the table structure eg add PK etc). Or uses VIEW or table to do repeat Full Load ONLY replication.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Regards,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;John.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 30 Nov 2022 10:27:17 GMT</pubDate>
    <dc:creator>john_wang</dc:creator>
    <dc:date>2022-11-30T10:27:17Z</dc:date>
    <item>
      <title>Replication of MS SQL Server table with Columnstore Index</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/Replication-of-MS-SQL-Server-table-with-Columnstore-Index/m-p/2010628#M4362</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;This is noted within the limitations of Qlik but is there a workaround for this issue?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Jian&lt;/P&gt;</description>
      <pubDate>Tue, 29 Nov 2022 21:53:22 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/Replication-of-MS-SQL-Server-table-with-Columnstore-Index/m-p/2010628#M4362</guid>
      <dc:creator>jmiao</dc:creator>
      <dc:date>2022-11-29T21:53:22Z</dc:date>
    </item>
    <item>
      <title>Re: Replication of MS SQL Server table with Columnstore Index</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/Replication-of-MS-SQL-Server-table-with-Columnstore-Index/m-p/2010631#M4363</link>
      <description>&lt;P&gt;Hi Jian,&lt;/P&gt;
&lt;P&gt;If this is a required use case, you can try using the ODBC with CDC endpoint as a workaround. However, as noted in the user guide, this needs to be communicated to your QDI Specialist and implemented thru Professional Services.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For your reference:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://help.qlik.com/en-US/replicate/November2022/Content/Replicate/Main/ODBC%20with%20CDC/odbc_source_with_CDC.htm" target="_blank"&gt;https://help.qlik.com/en-US/replicate/November2022/Content/Replicate/Main/ODBC%20with%20CDC/odbc_source_with_CDC.htm&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope this helps!&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;
&lt;P&gt;Lyka&lt;/P&gt;</description>
      <pubDate>Tue, 29 Nov 2022 22:02:49 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/Replication-of-MS-SQL-Server-table-with-Columnstore-Index/m-p/2010631#M4363</guid>
      <dc:creator>lyka</dc:creator>
      <dc:date>2022-11-29T22:02:49Z</dc:date>
    </item>
    <item>
      <title>Re: Replication of MS SQL Server table with Columnstore Index</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/Replication-of-MS-SQL-Server-table-with-Columnstore-Index/m-p/2010837#M4369</link>
      <description>&lt;P&gt;Hello &lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/165296"&gt;@jmiao&lt;/a&gt; ,&lt;/P&gt;
&lt;P&gt;Replicate provides 2 drivers to capture Microsoft SQL Server source DB changes. One way is reading changes from TLOG, another approach is using MS-CDC. However both of the drivers cannot get changes from &lt;SPAN&gt;table with Columnstore Index, this is because of Microsoft SQL Server itself limitation rather than Replicate limitation.  Here is the MS docs reference page &lt;A title="Columnstore indexes can't be combined with the following features" href="https://learn.microsoft.com/en-us/sql/t-sql/statements/create-columnstore-index-transact-sql?view=sql-server-ver15" target="_blank" rel="noopener"&gt;Columnstore indexes can't be combined with the following features&lt;/A&gt; .&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Totally agree with &lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/113691"&gt;@lyka&lt;/a&gt; , I think this is the one option (without change the table structure eg add PK etc). Or uses VIEW or table to do repeat Full Load ONLY replication.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Regards,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;John.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 30 Nov 2022 10:27:17 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/Replication-of-MS-SQL-Server-table-with-Columnstore-Index/m-p/2010837#M4369</guid>
      <dc:creator>john_wang</dc:creator>
      <dc:date>2022-11-30T10:27:17Z</dc:date>
    </item>
  </channel>
</rss>

