<?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>article Qlik Replicate Trigger SAP HANA conversion from Version 1 to Version 2 or Version 3 in Official Support Articles</title>
    <link>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Replicate-Trigger-SAP-HANA-conversion-from-Version-1-to/ta-p/2107737</link>
    <description>&lt;P&gt;The Qlik Replicate SAP HANA source endpoint allows you to convert to using the&amp;nbsp;&lt;STRONG&gt;log table&amp;nbsp;&lt;/STRONG&gt;with&amp;nbsp;&lt;STRONG&gt;CDC changes&lt;/STRONG&gt;. This article documents how to convert the&amp;nbsp;existing triggers into Version 2 or CTS Mode Version 3.&lt;/P&gt;
&lt;BLOCKQUOTE class="quote"&gt;Contact Qlik Support if you plan to convert your triggers, as additional migration steps may be needed to avoid data loss.&lt;/BLOCKQUOTE&gt;
&lt;H3&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;SAP HANA considered as running in “V1” mode:&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="V1 mode.png" style="width: 706px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/114909i6DEC506AA2CB16A4/image-size/large?v=v2&amp;amp;px=999" role="button" title="V1 mode.png" alt="V1 mode.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H4&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;V1 attrep_cdc_changes:&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H4&gt;
&lt;P&gt;When a task is started for the first time with HANA Trigger Based and without “Log Table” it will create the following artifacts:&lt;/P&gt;
&lt;UL class="lia-list-style-type-circle"&gt;
&lt;LI&gt;Table attrep_cdc_changes&lt;/LI&gt;
&lt;LI&gt;Triggers for insert/update/delete with “V1” in their trigger name, for each table in the task list.&lt;/LI&gt;
&lt;LI&gt;The resulting stream position LSN will always start with “V1:”.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;In “V1” mode, the INDX column of the attrep_cdc_changes table is used in the stream position for change data capture.&lt;/P&gt;
&lt;P&gt;NOTE:&amp;nbsp; The “V1” endpoint supports Advanced Run Start From Timestamp.&lt;/P&gt;
&lt;UL class="lia-list-style-type-circle"&gt;
&lt;LI&gt;the table &lt;FONT face="courier new,courier"&gt;attrep_cdc_changes&lt;/FONT&gt;&lt;/LI&gt;
&lt;LI&gt;triggers for &lt;FONT face="courier new,courier"&gt;insert/update/delete&lt;/FONT&gt; with &lt;FONT face="courier new,courier"&gt;v1&lt;/FONT&gt;&amp;nbsp;in their trigger name for each table in the task list&lt;/LI&gt;
&lt;LI&gt;the resulting stream position LSN will always start with &lt;FONT face="courier new,courier"&gt;V1:&lt;/FONT&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;SAP HANA considered as running in “V2” mode:&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="V2 mode.png" style="width: 695px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/114910i21EEBA21104A725A/image-size/large?v=v2&amp;amp;px=999" role="button" title="V2 mode.png" alt="V2 mode.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H4&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;V2 attrep_cdc_changes plus attrep_cdc_log:&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H4&gt;
&lt;P&gt;When Log Table is enabled (Advanced tab) the endpoint will be considered to be running in “V2” mode.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Migrated endpoints: For existing “V1” endpoints being migrated to “v2”, the customer must manually create the necessary attrep_cdc_log table and follow the instructions for switching into this mode.&amp;nbsp;&amp;nbsp; The underlying table triggers will still show “v1” in their name.&amp;nbsp; If the “SAP Archiving User” filter is specified, the following steps will happen when the task using this endpoint is resumed:&lt;/P&gt;
&lt;UL class="lia-list-style-type-circle"&gt;
&lt;LI&gt;“v1” triggers will be dropped.&lt;/LI&gt;
&lt;LI&gt;“v2” triggers will be created.&lt;/LI&gt;
&lt;LI&gt;attrep_cdc_log and attrep_cdc_changes will be altered to add an APPLICATION_USER column to each table.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;Contact Support for more migration instructions when moving from “V1” to V2”.&lt;/P&gt;
&lt;P&gt;New endpoints: For new endpoints in new artifact schemas (no prior attrep* tables), the “V2” endpoint upon first usage will create both attrep_cdc_changes and attrep_cdc_log tables. All table triggers will be “v2”.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In “V2” mode, the $rowid$ column of attrep_cdc_log is used in the stream position for change data capture.&lt;/P&gt;
&lt;P&gt;Artifacts involved in “V2” mode are:&lt;/P&gt;
&lt;UL class="lia-list-style-type-circle"&gt;
&lt;LI&gt;Tables attrep_cdc_changes from before&lt;/LI&gt;
&lt;LI&gt;Table attrep_cdc_log&lt;/LI&gt;
&lt;LI&gt;“v1” triggers from before or “v2” triggers (not both).&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;STRONG&gt;NOTE:&lt;/STRONG&gt; The “V2” endpoint does not support Advanced Run Start From Timestamp. Use the following special query to create the LSN for Advanced Run:&lt;/P&gt;
&lt;PRE&gt;SELECT&amp;nbsp;'V1:'||MIN("$rowid$")||':'||MAX("$rowid$")||':0:'||MIN("$rowid$") AS&amp;nbsp;"STREAM POSITION"&amp;nbsp;from&amp;nbsp;"$SCHEMA$"."attrep_cdc_log"&amp;nbsp;WHERE&amp;nbsp;"CHANGE_EVENT_TIME"&amp;nbsp;&amp;gt;=&amp;nbsp;'YYYY-MM-DD HH:MM:SS'&lt;/PRE&gt;
&lt;P&gt;The &lt;STRONG&gt;LSN&lt;/STRONG&gt; for “&lt;STRONG&gt;V1&lt;/STRONG&gt;” and “&lt;STRONG&gt;V2&lt;/STRONG&gt;” endpoints both start with “&lt;STRONG&gt;V1&lt;/STRONG&gt;:”.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;SAP HANA considered as running in “V3” mode: &lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;BLOCKQUOTE class="quote"&gt;CTS Mode must be enabled on SAP HANA&lt;/BLOCKQUOTE&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="V3 mode.png" style="width: 719px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/114912iDAE97A2AE3677366/image-size/large?v=v2&amp;amp;px=999" role="button" title="V3 mode.png" alt="V3 mode.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;Open&amp;nbsp;&lt;STRONG&gt;More Options&lt;/STRONG&gt;,&lt;/LI&gt;
&lt;LI&gt;Click into the&amp;nbsp;&lt;STRONG&gt;Add feature name&amp;nbsp;&lt;/STRONG&gt;textbox&amp;nbsp;and enter:&amp;nbsp;&lt;FONT face="courier new,courier"&gt;sapHanaCtsMode &lt;/FONT&gt;&lt;/LI&gt;
&lt;LI&gt;Use value &lt;FONT face="courier new,courier"&gt;&lt;STRONG&gt;On&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/LI&gt;
&lt;LI&gt;Click &lt;STRONG&gt;Add&amp;nbsp;&lt;/STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="saphanactsmode.png" style="width: 621px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/114915i1C499C5751B51042/image-size/large?v=v2&amp;amp;px=999" role="button" title="saphanactsmode.png" alt="saphanactsmode.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;
&lt;/OL&gt;
&lt;H4&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;V3 attrep_cdc_changes_cts, known as “CTS Mode”&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H4&gt;
&lt;P&gt;A “V3” endpoint can be created, or a “V1” or “V2” endpoint can be modified.&amp;nbsp; In both cases a new Feature Flag &lt;STRONG&gt;sapHanaCtsMode&lt;/STRONG&gt; must be added and set to ON. In addition for the “V2” endpoint being converted to “V3” the “Log Table” Advanced parameter must be unchecked.&lt;/P&gt;
&lt;P&gt;When the task using this endpoint is started for the first time the following steps will be performed:&lt;/P&gt;
&lt;UL class="lia-list-style-type-circle"&gt;
&lt;LI&gt;Table attrep_cdc_changes_cts will be created.&lt;/LI&gt;
&lt;LI&gt;“v3” triggers will be created for each table in the task list.&lt;/LI&gt;
&lt;LI&gt;The old “V1” and “V2” tables will not be removed.&lt;/LI&gt;
&lt;LI&gt;The old “v1” and/or “v2” triggers will not be removed.&lt;/LI&gt;
&lt;LI&gt;The internal LSNs will start with “V3:”.&lt;/LI&gt;
&lt;LI&gt;The stream position will be based on internal column $rowcts$ from table attrep_cdc_changes_cts.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;Note that:&lt;/P&gt;
&lt;UL class="lia-list-style-type-circle"&gt;
&lt;LI&gt;to avoid data loss when moving to V3, tables should be fully reloaded.&amp;nbsp; Alternatively, a set of migration steps may be carefully followed.&amp;nbsp; Contact Support for those details.&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;CTS Mode DOES support SAP Archive User filtering when specified on the endpoint.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;“V3” mode does support Advanced Run Start From Timestamp.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;&lt;STRONG&gt;&lt;FONT color="#339966"&gt;Related Content&lt;/FONT&gt;&lt;/STRONG&gt;&amp;nbsp;&lt;/H3&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&lt;A href="https://community.qlik.com/t5/Official-Support-Articles/How-to-enable-SAP-HANA-CTS-Mode-support-in-Qlik-Replicate/ta-p/2077967" target="_blank" rel="noopener"&gt;How to enable SAP HANA CTS Mode support in Qlik Replicate&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H4&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Environment&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H4&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&lt;LI-PRODUCT title="Qlik Replicate" id="qlikReplicate"&gt;&lt;/LI-PRODUCT&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 28 Aug 2024 08:21:49 GMT</pubDate>
    <dc:creator>Bill_Steinagle</dc:creator>
    <dc:date>2024-08-28T08:21:49Z</dc:date>
    <item>
      <title>Qlik Replicate Trigger SAP HANA conversion from Version 1 to Version 2 or Version 3</title>
      <link>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Replicate-Trigger-SAP-HANA-conversion-from-Version-1-to/ta-p/2107737</link>
      <description>&lt;P&gt;The Qlik Replicate SAP HANA source endpoint allows you to convert to using the&amp;nbsp;&lt;STRONG&gt;log table&amp;nbsp;&lt;/STRONG&gt;with&amp;nbsp;&lt;STRONG&gt;CDC changes&lt;/STRONG&gt;. This article documents how to convert the&amp;nbsp;existing triggers into Version 2 or CTS Mode Version 3.&lt;/P&gt;
&lt;BLOCKQUOTE class="quote"&gt;Contact Qlik Support if you plan to convert your triggers, as additional migration steps may be needed to avoid data loss.&lt;/BLOCKQUOTE&gt;
&lt;H3&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;SAP HANA considered as running in “V1” mode:&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="V1 mode.png" style="width: 706px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/114909i6DEC506AA2CB16A4/image-size/large?v=v2&amp;amp;px=999" role="button" title="V1 mode.png" alt="V1 mode.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H4&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;V1 attrep_cdc_changes:&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H4&gt;
&lt;P&gt;When a task is started for the first time with HANA Trigger Based and without “Log Table” it will create the following artifacts:&lt;/P&gt;
&lt;UL class="lia-list-style-type-circle"&gt;
&lt;LI&gt;Table attrep_cdc_changes&lt;/LI&gt;
&lt;LI&gt;Triggers for insert/update/delete with “V1” in their trigger name, for each table in the task list.&lt;/LI&gt;
&lt;LI&gt;The resulting stream position LSN will always start with “V1:”.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;In “V1” mode, the INDX column of the attrep_cdc_changes table is used in the stream position for change data capture.&lt;/P&gt;
&lt;P&gt;NOTE:&amp;nbsp; The “V1” endpoint supports Advanced Run Start From Timestamp.&lt;/P&gt;
&lt;UL class="lia-list-style-type-circle"&gt;
&lt;LI&gt;the table &lt;FONT face="courier new,courier"&gt;attrep_cdc_changes&lt;/FONT&gt;&lt;/LI&gt;
&lt;LI&gt;triggers for &lt;FONT face="courier new,courier"&gt;insert/update/delete&lt;/FONT&gt; with &lt;FONT face="courier new,courier"&gt;v1&lt;/FONT&gt;&amp;nbsp;in their trigger name for each table in the task list&lt;/LI&gt;
&lt;LI&gt;the resulting stream position LSN will always start with &lt;FONT face="courier new,courier"&gt;V1:&lt;/FONT&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;SAP HANA considered as running in “V2” mode:&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="V2 mode.png" style="width: 695px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/114910i21EEBA21104A725A/image-size/large?v=v2&amp;amp;px=999" role="button" title="V2 mode.png" alt="V2 mode.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H4&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;V2 attrep_cdc_changes plus attrep_cdc_log:&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H4&gt;
&lt;P&gt;When Log Table is enabled (Advanced tab) the endpoint will be considered to be running in “V2” mode.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Migrated endpoints: For existing “V1” endpoints being migrated to “v2”, the customer must manually create the necessary attrep_cdc_log table and follow the instructions for switching into this mode.&amp;nbsp;&amp;nbsp; The underlying table triggers will still show “v1” in their name.&amp;nbsp; If the “SAP Archiving User” filter is specified, the following steps will happen when the task using this endpoint is resumed:&lt;/P&gt;
&lt;UL class="lia-list-style-type-circle"&gt;
&lt;LI&gt;“v1” triggers will be dropped.&lt;/LI&gt;
&lt;LI&gt;“v2” triggers will be created.&lt;/LI&gt;
&lt;LI&gt;attrep_cdc_log and attrep_cdc_changes will be altered to add an APPLICATION_USER column to each table.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;Contact Support for more migration instructions when moving from “V1” to V2”.&lt;/P&gt;
&lt;P&gt;New endpoints: For new endpoints in new artifact schemas (no prior attrep* tables), the “V2” endpoint upon first usage will create both attrep_cdc_changes and attrep_cdc_log tables. All table triggers will be “v2”.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In “V2” mode, the $rowid$ column of attrep_cdc_log is used in the stream position for change data capture.&lt;/P&gt;
&lt;P&gt;Artifacts involved in “V2” mode are:&lt;/P&gt;
&lt;UL class="lia-list-style-type-circle"&gt;
&lt;LI&gt;Tables attrep_cdc_changes from before&lt;/LI&gt;
&lt;LI&gt;Table attrep_cdc_log&lt;/LI&gt;
&lt;LI&gt;“v1” triggers from before or “v2” triggers (not both).&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;STRONG&gt;NOTE:&lt;/STRONG&gt; The “V2” endpoint does not support Advanced Run Start From Timestamp. Use the following special query to create the LSN for Advanced Run:&lt;/P&gt;
&lt;PRE&gt;SELECT&amp;nbsp;'V1:'||MIN("$rowid$")||':'||MAX("$rowid$")||':0:'||MIN("$rowid$") AS&amp;nbsp;"STREAM POSITION"&amp;nbsp;from&amp;nbsp;"$SCHEMA$"."attrep_cdc_log"&amp;nbsp;WHERE&amp;nbsp;"CHANGE_EVENT_TIME"&amp;nbsp;&amp;gt;=&amp;nbsp;'YYYY-MM-DD HH:MM:SS'&lt;/PRE&gt;
&lt;P&gt;The &lt;STRONG&gt;LSN&lt;/STRONG&gt; for “&lt;STRONG&gt;V1&lt;/STRONG&gt;” and “&lt;STRONG&gt;V2&lt;/STRONG&gt;” endpoints both start with “&lt;STRONG&gt;V1&lt;/STRONG&gt;:”.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;SAP HANA considered as running in “V3” mode: &lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;BLOCKQUOTE class="quote"&gt;CTS Mode must be enabled on SAP HANA&lt;/BLOCKQUOTE&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="V3 mode.png" style="width: 719px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/114912iDAE97A2AE3677366/image-size/large?v=v2&amp;amp;px=999" role="button" title="V3 mode.png" alt="V3 mode.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;Open&amp;nbsp;&lt;STRONG&gt;More Options&lt;/STRONG&gt;,&lt;/LI&gt;
&lt;LI&gt;Click into the&amp;nbsp;&lt;STRONG&gt;Add feature name&amp;nbsp;&lt;/STRONG&gt;textbox&amp;nbsp;and enter:&amp;nbsp;&lt;FONT face="courier new,courier"&gt;sapHanaCtsMode &lt;/FONT&gt;&lt;/LI&gt;
&lt;LI&gt;Use value &lt;FONT face="courier new,courier"&gt;&lt;STRONG&gt;On&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/LI&gt;
&lt;LI&gt;Click &lt;STRONG&gt;Add&amp;nbsp;&lt;/STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="saphanactsmode.png" style="width: 621px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/114915i1C499C5751B51042/image-size/large?v=v2&amp;amp;px=999" role="button" title="saphanactsmode.png" alt="saphanactsmode.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;
&lt;/OL&gt;
&lt;H4&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;V3 attrep_cdc_changes_cts, known as “CTS Mode”&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H4&gt;
&lt;P&gt;A “V3” endpoint can be created, or a “V1” or “V2” endpoint can be modified.&amp;nbsp; In both cases a new Feature Flag &lt;STRONG&gt;sapHanaCtsMode&lt;/STRONG&gt; must be added and set to ON. In addition for the “V2” endpoint being converted to “V3” the “Log Table” Advanced parameter must be unchecked.&lt;/P&gt;
&lt;P&gt;When the task using this endpoint is started for the first time the following steps will be performed:&lt;/P&gt;
&lt;UL class="lia-list-style-type-circle"&gt;
&lt;LI&gt;Table attrep_cdc_changes_cts will be created.&lt;/LI&gt;
&lt;LI&gt;“v3” triggers will be created for each table in the task list.&lt;/LI&gt;
&lt;LI&gt;The old “V1” and “V2” tables will not be removed.&lt;/LI&gt;
&lt;LI&gt;The old “v1” and/or “v2” triggers will not be removed.&lt;/LI&gt;
&lt;LI&gt;The internal LSNs will start with “V3:”.&lt;/LI&gt;
&lt;LI&gt;The stream position will be based on internal column $rowcts$ from table attrep_cdc_changes_cts.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;Note that:&lt;/P&gt;
&lt;UL class="lia-list-style-type-circle"&gt;
&lt;LI&gt;to avoid data loss when moving to V3, tables should be fully reloaded.&amp;nbsp; Alternatively, a set of migration steps may be carefully followed.&amp;nbsp; Contact Support for those details.&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;CTS Mode DOES support SAP Archive User filtering when specified on the endpoint.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;“V3” mode does support Advanced Run Start From Timestamp.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;&lt;STRONG&gt;&lt;FONT color="#339966"&gt;Related Content&lt;/FONT&gt;&lt;/STRONG&gt;&amp;nbsp;&lt;/H3&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&lt;A href="https://community.qlik.com/t5/Official-Support-Articles/How-to-enable-SAP-HANA-CTS-Mode-support-in-Qlik-Replicate/ta-p/2077967" target="_blank" rel="noopener"&gt;How to enable SAP HANA CTS Mode support in Qlik Replicate&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H4&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Environment&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H4&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&lt;LI-PRODUCT title="Qlik Replicate" id="qlikReplicate"&gt;&lt;/LI-PRODUCT&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 28 Aug 2024 08:21:49 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Replicate-Trigger-SAP-HANA-conversion-from-Version-1-to/ta-p/2107737</guid>
      <dc:creator>Bill_Steinagle</dc:creator>
      <dc:date>2024-08-28T08:21:49Z</dc:date>
    </item>
  </channel>
</rss>

