Re: SQL Result Paging

[Alan Campin <alan0307d@xxxxxxxxx>]

A stored procedure would probably work in this case.

Briefly.

Send query to stored procedure.

If page number = 1
  Select all rows into a temp table or even faster a user space using fetch
n rows, then return only first n records.
else
  Return only page number records

A stored procedure maintains state so when you came back the second time,
the data will still be there from the first time so you could send only
whether page number you need.



On Mon, Mar 11, 2013 at 1:28 PM, Mike Wills <mike@xxxxxxxxxxxx> wrote:

> I have a query that is sub-second. When I run it on the green-screen, I get
> a result as soon as I hit "enter". So I know that that query itself isn't
> the problem. I am returning around 800 results.
>
> However, when I pipe it through my C# ASP.NET application, it takes
> FOREVER
> (okay 3 minutes), but lets be honest, that is forever in the web world.
>
> My question is, how do I go about adding paging to my query. I found this
> 400 Guru article (http://www.itjungle.com/fhg/fhg111109-story01.html), but
> was wondering if there were other ways. Maybe using a stored procedure or
> something?
>
> --
> Mike Wills
> http://mikewills.me
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.