DBGrid with big DataSet

[skafy]

How can I handle big dataset in TUniDBGrid with 100k+ records. For now I have FetchAll prop ON, but it it slow. how can  I handle this type of situacion?

[adragan]

First I don't see the use of browsing 100k+ records in a DBGrid. I don't think the result is relevant for anything.

Why don't you try some quey that returns a relevant result set, like 100+ records that mean something.

Some other solution would be a query like "select first 100 skip <n*100>  from ........ order by id" , save the position

in some varible and with some buttons go forward or backward as needed recalculating the "n".

[rencarnacion]

All my Queries for master table consult are limited to 1000 record , only for report I always load all record from the query 

[jahlxx]

don't fetch all and page the grid

[skafy]

If I would then fetch 100 - 1000 records, then I should I implement logics for next page and last page. But how would I then filter and sort records. Now I use FDQuery.Filter and FDQuery.Indexes for sort.

[zilav]

Big data is filtered on server, not on client. Rewrite your queries to accept search/filter parameters and return a limited result set.