I realize this question isn't only about WebDataGrid, but it's related so, maybe it won't be considered offtopic.
I have a TSQL stored procedure that can run for a few minutes and return a few million records, I need to display that data in WebDataGrid. Obviously I don't want return all data at once and need to setup some kind of paging options - every time user selects another page - another portion of data is loaded from the DB. But I can't run the SP every time new page is requested - it would take too much time.
What would be the best way to persist data from the SP, so when user selects a new page - new data portion would be loaded by a simple SELECT... WHERE from that temp data storage?
Hi ygalanter,
I would suggest that you check the following sample of custom databinding, depending on the grid's paging - http://samples.infragistics.com/aspnet/Samples/WebDataGrid/Data/Custom-DataBinding-Paging-Collection/Default.aspx?cn=data-grid&sid=56a2a94a-12e4-4108-a480-ff4bbf85852b.
Please let me know if this helps.
Thanks for the prompt reply, but that sample still retrieves full set of data before limiting it to the current page, not a real-life scenario.
In my case I cannot retrieve full resultset every time (it'sa long-running stored procedure), I need to temporarily store it somewhere, so I can cut it to custom ranges for custom databinding.
Any idea on how to implement this?