Yeah, normal iterations that select most/all columns like
for row in customers
and similar...However I see that kdb+ is column-store (http://www.timestored.com/kdb-guides/kdb-database-intro) and supposedly the performance is ok?
Sequential scans form the core of most column store queries, why would iteration be an issue? Do you mean iterations considering multiple fields of a structure or similar? In that case, you should be able to break that into a series of efficient, per-column queries which can be lazily materialized.
[0] http://db.csail.mit.edu/projects/cstore/abadi-sigmod08.pdf