Actually i am really confused regarding paging activity
I want to implement paging in asp.net but i am not able to take out
the idea regarding
how to implement the concept for large databases where the tables r
containing 1000s of records
Problem is:I cannot save the dataset in session as it will b too
costly and all the time i cannot access the database as database
transasction require costly operations
can anyone plz tell me the solution regarding optimizing this problem
Mr. Arnold - 15 Sep 2007 20:07 GMT
> Actually i am really confused regarding paging activity
>
[quoted text clipped - 7 lines]
> transasction require costly operations
> can anyone plz tell me the solution regarding optimizing this problem
That's why one uses a SQL Server State server, where you can hold a dataset
in Session. And I don't see why you cannot use ADO.NET's transactional
features. It's just as costly having to go back to SQL Server, pulling
those records over again and again, because the user is going to or
returning to the page. This is also a question for a ASP.NET NG, which is on
msnews.micorsoft,com as well.
Peter Bromberg [C# MVP] - 16 Sep 2007 14:34 GMT
The solution is over at the asp.net newsgroup
http://msdn.microsoft.com/newsgroups/default.aspx?pg=1&guid=&sloc=en-us&dg=micro
soft.public.dotnet.framework.aspnet&fltr=
-- this is the C# language group, which really doesn't cover ASP.NET paging.
--Peter
Recursion: see Recursion
site: http://www.eggheadcafe.com
unBlog: http://petesbloggerama.blogspot.com
BlogMetaFinder: http://www.blogmetafinder.com
> Actually i am really confused regarding paging activity
>
[quoted text clipped - 7 lines]
> transasction require costly operations
> can anyone plz tell me the solution regarding optimizing this problem