Skip to main content
To homepage To homepage

Hello,

I have the following setup for an incrementally loaded table:

I would expect, that it loads all rows, with either an id greater than max id - 1000 or datum_post greater than max datum_post - one week.

In fact, when I execute the query, it is not returning any rows. This is interesting, because removing the datum_post condition returns rows.

Other tables with such a double condition (id + date) also work. I am wondering, whether it is necessary to have an index on datum_post in the source table? The queries can take quite a while on the datum_post field. The example query takes 2 minutes on the source database, but TimeXtender finishes after 30 seconds. TimeXtender says it is finished with "Success", but there are no rows.

Also the following query yields results when querying the source database directly: 

I think this is the equivalent query to what TimeXtender should load.

I am using Discovery Hub 19.6.7.64 and the source database is using (an old) mysql version: 

I am connecting with it using the CData ADO.NET Provider for MySQL 2019 (19.0.7118.0).

Regards,

Hendrik Gruß

 

Ok, I figured out, that the timeout was the problem.


There is no error message, but when using the advanced > query tool feature on the source table in TimeXtender and doing the query, a timeout error was thrown.


The problem was, that the timeout on the datasource was set to 0 (I thought that menas no timeout). I set it to 200 and now it works.

Reply


Terms and ConditionsCookie settings