A virtualized grid does not mean the data request is virtualized all the way to the sql server. The main issue with displaying 100,000 rows in the browser is D

A virtualized grid does not mean the data request is virtualized all the way to the sql server. The main issue with displaying 100,000 rows in the browser is DOM overhead. A virtualized grid like Slickgrid which they are using, reuses dom elements as you scroll and in its simplest form is just backed by an in-memory JS object. Once you start exceeding what works well in memory you can move to a local temp file system, which it sounds like what they are doing. None of this has anything to do with the SQL server itself, it simply sends the entire result set to the client which deals with buffering and virtualizing it to the UI in whatever way necessary. This is how native SQL UI's tend to work, I have never seen one rewrite SQL to try and virtualize all the way to the DB. Obviously unless you do use the DB there will be limits, but 100,000 rows fits entirely in memory without issue: checkout this sample: http://mleibman.github.io/SlickGrid/examples/example-optimizing-dataview.html http://mleibman.github.io/SlickGrid/examples/example-optimiz...