db query reader - fetching problem

[MartinDDDD]

Yes and No: In azure cloud we had to add some sort of credits to have more computing resources allocated which ended up speeding up queries that were send from Knime nodes to SQL DB on Azure.

Issue we found was that the query processing on DB was the issue - not the Knime node - I.e. the knime node took so long because there was a demanding query being processed in the cloud

Edit: Found a post I made on a similar topic:

Read millions of records from table

Hey there, welcome to the forum. If you are using DB query reader node the query is executed in the DB - so the performance bottle neck is likely the DB itself that takes time to execute the query. In the past I had use cases that initially used a DB on MS Azure - as the DB grew and the amounts of data queries returned grew larger, we opted to purchase additional Database Transaction Units, which simply spoken increases cloud resources and consequently make things faster. Luckily at some stag…

The term I couldn’t remember was Database Transaction Units (DTUs), that we had to increase to speed up query processing