https://community.qlik.com/t5/Connectivity-Data-Prep/Azure-OLEDB-Data-Connection-Issues-Slowness/m-p/1602491#M4174 <P>We have Qlik Sense leveraging the OLEDB option to connect to a third party application on an Azure environment using a read only SQL Server user.&nbsp; All was well connecting to the various database tables in this environment, for a few years now.&nbsp; Recently, we've had issues where it appears that on the 13th or so each month...the OLEDB connection ends up performing at a snails pace, and our extracts are not able to complete.&nbsp; We end up losing our connection with the application.&nbsp; When we point to the same Qlik instance to a Test version of the same application the OLEDB performance works as expected...pulling 200,000 plus rows of data at a time, where as our production environment is pulling around 30,000 rows at a time for a particular table...where it eventual times out.&nbsp; I believe our partner has moved our application to a different Azure server to correct the issue, but is there a known network or server setting that could be causing this issue to limit the number of rows we are able to extract at a given time?&nbsp; Trying to point the teams in the right direction.</P> Tue, 21 Dec 2021 13:43:01 GMT gamaescalante 2021-12-21T13:43:01Z https://community.qlik.com/t5/Connectivity-Data-Prep/Azure-OLEDB-Data-Connection-Issues-Slowness/m-p/1602491#M4174 <P>We have Qlik Sense leveraging the OLEDB option to connect to a third party application on an Azure environment using a read only SQL Server user.&nbsp; All was well connecting to the various database tables in this environment, for a few years now.&nbsp; Recently, we've had issues where it appears that on the 13th or so each month...the OLEDB connection ends up performing at a snails pace, and our extracts are not able to complete.&nbsp; We end up losing our connection with the application.&nbsp; When we point to the same Qlik instance to a Test version of the same application the OLEDB performance works as expected...pulling 200,000 plus rows of data at a time, where as our production environment is pulling around 30,000 rows at a time for a particular table...where it eventual times out.&nbsp; I believe our partner has moved our application to a different Azure server to correct the issue, but is there a known network or server setting that could be causing this issue to limit the number of rows we are able to extract at a given time?&nbsp; Trying to point the teams in the right direction.</P> Tue, 21 Dec 2021 13:43:01 GMT https://community.qlik.com/t5/Connectivity-Data-Prep/Azure-OLEDB-Data-Connection-Issues-Slowness/m-p/1602491#M4174 gamaescalante 2021-12-21T13:43:01Z https://community.qlik.com/t5/Connectivity-Data-Prep/Azure-OLEDB-Data-Connection-Issues-Slowness/m-p/2503794#M14531 <P>We have the same issue. Were you able to solve?</P> Thu, 30 Jan 2025 17:15:08 GMT https://community.qlik.com/t5/Connectivity-Data-Prep/Azure-OLEDB-Data-Connection-Issues-Slowness/m-p/2503794#M14531 isabella_santi 2025-01-30T17:15:08Z