https://community.qlik.com/t5/Suggest-an-Idea/Qlik-Replicate-data-loss-with-Microsoft-SQL-endpoint-when-using/idc-p/1793545#M5571 <P>Cases should be&nbsp;02132773&nbsp; &amp;&nbsp;<SPAN>02153309&nbsp;</SPAN></P> Tue, 23 Mar 2021 02:18:37 GMT mgarret2 2021-03-23T02:18:37Z https://community.qlik.com/t5/Suggest-an-Idea/Qlik-Replicate-data-loss-with-Microsoft-SQL-endpoint-when-using/idi-p/1783562 <P>We have many&nbsp;<SPAN>Microsoft SQL Server end points.&nbsp; Due to the way our SQL backups are configured, we have the&nbsp;<STRONG>Change processing mode (read changes from):&nbsp;</STRONG> set with the <STRONG>Online Logs only.&nbsp; &nbsp;</STRONG>What we have found, and confirmed with Qlik support, is that when Replicate can not find the needed LSN it will move forward to the first available&nbsp;LSN.&nbsp; There is no warning nor error message in the logs when this happens.&nbsp; Therefore, we miss processing of source transactions with no awareness of the loss.</SPAN></P><P><SPAN>When the option&nbsp; is set to Prioritize&nbsp;Online Logs the tool will provide an error that the needed LSN can not be found.&nbsp; We find this discrepancy in behavior to be unacceptable.&nbsp; A replication tool should never skip data without an error.&nbsp; We would like to see an option to error out when <STRONG>Online Logs Only</STRONG> is selected and a needed LSN is not available.&nbsp;</SPAN></P> Wed, 17 Feb 2021 19:59:18 GMT https://community.qlik.com/t5/Suggest-an-Idea/Qlik-Replicate-data-loss-with-Microsoft-SQL-endpoint-when-using/idi-p/1783562 mgarret2 2021-02-17T19:59:18Z https://community.qlik.com/t5/Suggest-an-Idea/Qlik-Replicate-data-loss-with-Microsoft-SQL-endpoint-when-using/idc-p/1792616#M5540 <P>Could you share your support case number for this issue?&nbsp;&nbsp;</P> Thu, 18 Mar 2021 15:51:05 GMT https://community.qlik.com/t5/Suggest-an-Idea/Qlik-Replicate-data-loss-with-Microsoft-SQL-endpoint-when-using/idc-p/1792616#M5540 Shelley_Brennan 2021-03-18T15:51:05Z https://community.qlik.com/t5/Suggest-an-Idea/Qlik-Replicate-data-loss-with-Microsoft-SQL-endpoint-when-using/idc-p/1793545#M5571 <P>Cases should be&nbsp;02132773&nbsp; &amp;&nbsp;<SPAN>02153309&nbsp;</SPAN></P> Tue, 23 Mar 2021 02:18:37 GMT https://community.qlik.com/t5/Suggest-an-Idea/Qlik-Replicate-data-loss-with-Microsoft-SQL-endpoint-when-using/idc-p/1793545#M5571 mgarret2 2021-03-23T02:18:37Z https://community.qlik.com/t5/Suggest-an-Idea/Qlik-Replicate-data-loss-with-Microsoft-SQL-endpoint-when-using/idc-p/1804625#M6084 <P>This will be addressed in May 2021 release.&nbsp; Thanks!</P> Mon, 03 May 2021 13:14:57 GMT https://community.qlik.com/t5/Suggest-an-Idea/Qlik-Replicate-data-loss-with-Microsoft-SQL-endpoint-when-using/idc-p/1804625#M6084 Shelley_Brennan 2021-05-03T13:14:57Z https://community.qlik.com/t5/Suggest-an-Idea/Qlik-Replicate-data-loss-with-Microsoft-SQL-endpoint-when-using/idc-p/1807814#M6217 <P>Addressed in the May 2021 release.&nbsp; Thank you!</P> Thu, 13 May 2021 15:23:33 GMT https://community.qlik.com/t5/Suggest-an-Idea/Qlik-Replicate-data-loss-with-Microsoft-SQL-endpoint-when-using/idc-p/1807814#M6217 Shelley_Brennan 2021-05-13T15:23:33Z