Charger TransactionLinesIncremental dans Qlik provoque une \"System.OutOfMemoryException\"

The request 0HNE7KSAM1E3M:00000003 on Invantive App Online was terminated by the OData consumer (Qlik in this case) dropping the connection after 19 minutes and 14 seconds. It received 78.028 rows sofar on 1 partition.

The actual row count can easily be assessed in typically less than a second using the approach explained in:

using a query such as:

select *
from   rowcounts@eol
where  table_name = 'SyncTransactionLines'

For now, it will be assumed that 1-2 million rows are to be expected. Also, the nature of the design of *Incremental tables means that data can only start to return once all rows have been collected for a partition. Since there is only 1 partition selected, this means that the data collection has already ended at this moment in time and Invantive App Online is streaming rows to the OData consumer typically limited only by the bandwidth between producer and consumer.

A volume of 1-2 million rows should not be an issue. As of July 2025, Invantive Cloud is typically starting to get overstretched when there are 4 million or more rows per partition. Larger volumes with tens or hundreds of millions of rows on Exact Online or other cloud platforms will definitely exceed the current specifications for the current configuration of the Invantive Cloud. For these scenarios, the enterprise products are recommended such as on-premises Data Hub or on-premises UniversalSQL Server.

For now, there is no reason to expect any problem on the Invantive Cloud side.

A Google search revealed that the OutOfMemoryException sometimes appears on Qlik. See for instance:

The last one describes an Out of Memory-exception with 500.000 rows. This Qlik community post refers to Solved: " System.OutofMemoryException " appears when i loa... - Qlik Community - 1977929 which might be helpful.

Please note the typical uncompressed size of a dataset of 2 million transaction line rows will be in the range of 2 to 4 GiB.