<?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>idea Option to Add Supplemental Logging for All columns on Database tables in Suggest an Idea</title>
    <link>https://community.qlik.com/t5/Suggest-an-Idea/Option-to-Add-Supplemental-Logging-for-All-columns-on-Database/idi-p/1707911</link>
    <description>&lt;P&gt;Within&amp;nbsp;&lt;SPAN&gt;Qlik Replicate &amp;amp; Enterprise Manager you have an option to add supplemental logging to a source end point.&amp;nbsp; The supplemental logging that is generated by the application is specific to the make up of the table.&amp;nbsp; If the table contains a PK then only the PK and changed fields are logged during an update.&amp;nbsp; If the table has a UK then only the fields of the UK and changed fields are logged.&amp;nbsp; If there is no UK/PK then all columns are logged.&amp;nbsp; We would like an option to override this behavior and log all columns for all types of tables.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Here is why this is important.&amp;nbsp; The replicate product has an option to create change tables as part of the integration.&amp;nbsp; The change tables can be leveraged for downstream processing to understand what has changed and only process those changes.&amp;nbsp; Driving off the key may not be what downstream applications use to determine change.&amp;nbsp; In our example a table is keyed by PO number but the downstream change is driven off the product number.&amp;nbsp; The product number, not being a key or changed, does not appear in the change table.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Adding supplemental logging can be done manually but needs to be done every time a new table is added.&amp;nbsp; This option would eliminate the need for a manual work around.&lt;/P&gt;</description>
    <pubDate>Wed, 03 Jun 2020 17:24:50 GMT</pubDate>
    <dc:creator>Troy</dc:creator>
    <dc:date>2020-06-03T17:24:50Z</dc:date>
    <item>
      <title>Option to Add Supplemental Logging for All columns on Database tables</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/Option-to-Add-Supplemental-Logging-for-All-columns-on-Database/idi-p/1707911</link>
      <description>&lt;P&gt;Within&amp;nbsp;&lt;SPAN&gt;Qlik Replicate &amp;amp; Enterprise Manager you have an option to add supplemental logging to a source end point.&amp;nbsp; The supplemental logging that is generated by the application is specific to the make up of the table.&amp;nbsp; If the table contains a PK then only the PK and changed fields are logged during an update.&amp;nbsp; If the table has a UK then only the fields of the UK and changed fields are logged.&amp;nbsp; If there is no UK/PK then all columns are logged.&amp;nbsp; We would like an option to override this behavior and log all columns for all types of tables.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Here is why this is important.&amp;nbsp; The replicate product has an option to create change tables as part of the integration.&amp;nbsp; The change tables can be leveraged for downstream processing to understand what has changed and only process those changes.&amp;nbsp; Driving off the key may not be what downstream applications use to determine change.&amp;nbsp; In our example a table is keyed by PO number but the downstream change is driven off the product number.&amp;nbsp; The product number, not being a key or changed, does not appear in the change table.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Adding supplemental logging can be done manually but needs to be done every time a new table is added.&amp;nbsp; This option would eliminate the need for a manual work around.&lt;/P&gt;</description>
      <pubDate>Wed, 03 Jun 2020 17:24:50 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/Option-to-Add-Supplemental-Logging-for-All-columns-on-Database/idi-p/1707911</guid>
      <dc:creator>Troy</dc:creator>
      <dc:date>2020-06-03T17:24:50Z</dc:date>
    </item>
    <item>
      <title>Re: Option to Add Supplemental Logging for All columns on Database tables - Status changed to: Open - Collecting Feedback</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/Option-to-Add-Supplemental-Logging-for-All-columns-on-Database/idc-p/1725347#M2759</link>
      <description />
      <pubDate>Mon, 06 Jul 2020 12:39:17 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/Option-to-Add-Supplemental-Logging-for-All-columns-on-Database/idc-p/1725347#M2759</guid>
      <dc:creator>Ola_Mayer</dc:creator>
      <dc:date>2020-07-06T12:39:17Z</dc:date>
    </item>
    <item>
      <title>Re: Option to Add Supplemental Logging for All columns on Database tables</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/Option-to-Add-Supplemental-Logging-for-All-columns-on-Database/idc-p/1845794#M7536</link>
      <description>&lt;P&gt;Adding to the above issue, we have the below one:&lt;/P&gt;&lt;P&gt;If supplemental logging is turned on for the PK columns, in case of delete in source table, Qlik is capturing the deleted row with CDC trans type=Delete as per settings. But with that row, Qlik is replicating another row with all NULL values in other columns and only value in the PK column to target Snowflake. And for this extra NULL values row, downstream application having problem to process.&lt;/P&gt;&lt;P&gt;We need a Option to Turn on the Supplemental Logging for All Columns in the Source DB tables.&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Sandip Saha&lt;/P&gt;</description>
      <pubDate>Tue, 12 Oct 2021 18:57:54 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/Option-to-Add-Supplemental-Logging-for-All-columns-on-Database/idc-p/1845794#M7536</guid>
      <dc:creator>qlik_admin_lm</dc:creator>
      <dc:date>2021-10-12T18:57:54Z</dc:date>
    </item>
    <item>
      <title>From now on, please track this idea from the Ideation por...</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/Option-to-Add-Supplemental-Logging-for-All-columns-on-Database/idc-p/2100763#M14012</link>
      <description>&lt;P&gt;From now on, please track this idea from the Ideation portal.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;A title="Link to new idea" href="https://ideation.qlik.com/app/#/case/270751" target="_blank" rel="noopener"&gt;Link to new idea&lt;/A&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Meghann&lt;/P&gt;&lt;P data-unlink="true"&gt;&lt;EM&gt;NOTE: Upon clicking this link 2 tabs may open - please feel free to close the one with a login page. If you &lt;STRONG&gt;only&lt;/STRONG&gt; see 1 tab with the login page, please try clicking this link first: &lt;STRONG&gt;&lt;A title="Authenticate me!" href="#" target="_blank" rel="noopener"&gt;Authenticate me!&lt;/A&gt;&lt;/STRONG&gt;&amp;nbsp;t&lt;/EM&gt;&lt;EM&gt;hen try the link above again. Ensure pop-up blocker is off.&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 02 Aug 2023 15:51:42 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/Option-to-Add-Supplemental-Logging-for-All-columns-on-Database/idc-p/2100763#M14012</guid>
      <dc:creator>Meghann_MacDonald</dc:creator>
      <dc:date>2023-08-02T15:51:42Z</dc:date>
    </item>
    <item>
      <title>Re: Option to Add Supplemental Logging for All columns on Database tables - Status changed to: Closed - Archived</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/Option-to-Add-Supplemental-Logging-for-All-columns-on-Database/idc-p/2100764#M14013</link>
      <description />
      <pubDate>Wed, 02 Aug 2023 15:51:44 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/Option-to-Add-Supplemental-Logging-for-All-columns-on-Database/idc-p/2100764#M14013</guid>
      <dc:creator>Ideation</dc:creator>
      <dc:date>2023-08-02T15:51:44Z</dc:date>
    </item>
  </channel>
</rss>

