https://community.qlik.com/t5/Connectivity-Data-Prep/MIssing-rows/m-p/1532301#M3537 <P>We had similar problems and switched to an ODBC connection.&nbsp; This requires installing the database drivers on the Qlik Sense server and creating the ODBC connection.</P> Fri, 18 Jan 2019 16:46:23 GMT jwjackso 2019-01-18T16:46:23Z https://community.qlik.com/t5/Connectivity-Data-Prep/MIssing-rows/m-p/1532179#M3536 <P>This is becoming a real problem.&nbsp; At first, it was oracle but now its spreading to postgre.</P><P>We are simply loading from a backend (no filters, no sorting) and the script just stops at what seems to be random places.</P><P>I ran the script with 3,500,000 rows result, write to qvd and drop the table.&nbsp; I run the script again and I get only 80,000.</P><P>I've read about others having similar problems and we've applied fixes (MEMLIMIT, etc) but so far nothing has worked and its only getting worse.</P><P>I don't know if this is a driver issue, a memory issue or something else.</P><P>I need to get to a root cause because its at the point where Qliksense is becoming unusable.</P> Wed, 15 Dec 2021 17:32:50 GMT https://community.qlik.com/t5/Connectivity-Data-Prep/MIssing-rows/m-p/1532179#M3536 markp201 2021-12-15T17:32:50Z https://community.qlik.com/t5/Connectivity-Data-Prep/MIssing-rows/m-p/1532301#M3537 <P>We had similar problems and switched to an ODBC connection.&nbsp; This requires installing the database drivers on the Qlik Sense server and creating the ODBC connection.</P> Fri, 18 Jan 2019 16:46:23 GMT https://community.qlik.com/t5/Connectivity-Data-Prep/MIssing-rows/m-p/1532301#M3537 jwjackso 2019-01-18T16:46:23Z