Aha, never noticed that before!
Interestingly, I was just looking at the MaxRecords property of TableRequestInfoV5 and spotted this:
Limiting the amount of transferred rows can reduce traffic between the
DataAbstract server (middle tier) and the DataAbstract client (front-end
tier). It will not affect traffic between the database and the
DataAbstract server. For reducing traffic between the database and the
DataAbstract server, you have to use other approaches, like Dynamic Where.
This suggests that all data is retrieved from the database but only a subset is then returned to the client. Two questions arise:
Q1: Why is this the case, surely it would be more logical and efficient for DA to construct a SELECT TOP statement so only the subset of rows are retrieved from the database?
Q2: Does the table's MaxRecords property function in the same way?