I think that I know the solution but I want to ask the field to find myself in a quandry. I have ASP.NET (C # 2.0 Framework) page which is used as a lookup. To do something with standard gridview control, 5 columns of data, hyperlink for the 6th column, the user has to choose to record.
My question leads to the 'possible' 100k record best performance in that gridview? As it stands now, before I ever give a sung result, before I curb some other brown hair. Gridview can display approximately 20 lines of data on the screen at one time for its resistor, so even after creating the data, I get 5000 pages. Adding to the Rolodex-type Search on Ege The biggest return set on 'J' gives me 35000 records (where 'X' is only 54).
Do I shorten Rollodex or is there
Edit: I have already stored procedure that populates this set for paging As Generic Type-TA suggests, then with paging on 'J', I will also get 1750 pages. I have so much data that the number of participants on given auto policy should be able to give the name given to the administrator, or partial search. 'Jones' has 120 9 records and 'Smith' is 2918, yet it creates reboot for the result set.
Edit # 2: added 'possible' 100k, there is no Guarentee that will have many records in the account, in the other hand it may be more: (
Autocomplete is your friend :)
Just enter the first 2 or 3 letters of the people , Then filter your searches.
With a dataset, I do not think that paging is such a kind of understanding.
A good example page for jQuery is
Comments
Post a Comment