MaxRecords to make db call faster

[dw]

Hello, all. We have a search page that can return many thousands of records
from a SQL Server 2000 database. We've noticed that it's slow -- mainly b/c
the stored procedure arranges the person's first, middle, last names into
'name' before returning the results. In addition, we're using recordset
paging (using Pagesize and Pagecount properties of the recordset). Will we
see a speed performance by using the Maxrecords property of the recordset?
Are there any examples with recordset paging? Thanks.

[Aaron Bertrand [MVP]]

Plenty of different approaches here:

[url]http://www.aspfaq.com/2120[/url]

Also, suggest doing the string operations on the name at the client, where
you have to treat each iteration in the loop anyway. This should reduce the
strain on the actual SQL call...

A



"dw" <cougarmana_NOSPAM@uncw.edu> wrote in message
news:uMHsyB%23GEHA.2408@TK2MSFTNGP10.phx.gbl...

> Hello, all. We have a search page that can return many thousands of

records

> from a SQL Server 2000 database. We've noticed that it's slow -- mainly

b/c

> the stored procedure arranges the person's first, middle, last names into
> 'name' before returning the results. In addition, we're using recordset
> paging (using Pagesize and Pagecount properties of the recordset). Will we
> see a speed performance by using the Maxrecords property of the recordset?
> Are there any examples with recordset paging? Thanks.
>
>

[dw]

Thanks, Aaron. However, we know how to do recordset paging; but returning
1100 records (even w/out the string concatenation) is slow. When we use
maxrecords, it limits the entire recordset. What we're trying to do is to
design the paging to just fetch the ones for that page, not the entire
recordset. Thanks.

"Aaron Bertrand [MVP]" <aaron@TRASHaspfaq.com> wrote in message
news:ui6JxY%23GEHA.3556@TK2MSFTNGP11.phx.gbl...

> Plenty of different approaches here:
>
> [url]http://www.aspfaq.com/2120[/url]
>
> Also, suggest doing the string operations on the name at the client, where
> you have to treat each iteration in the loop anyway. This should reduce

the

> strain on the actual SQL call...
>
> A
>
>
>
> "dw" <cougarmana_NOSPAM@uncw.edu> wrote in message
> news:uMHsyB%23GEHA.2408@TK2MSFTNGP10.phx.gbl...

> > Hello, all. We have a search page that can return many thousands of

> records

> > from a SQL Server 2000 database. We've noticed that it's slow -- mainly

> b/c

> > the stored procedure arranges the person's first, middle, last names

into

> > 'name' before returning the results. In addition, we're using recordset
> > paging (using Pagesize and Pagecount properties of the recordset). Will

we

> > see a speed performance by using the Maxrecords property of the

recordset?

> > Are there any examples with recordset paging? Thanks.
> >
> >

>
>

[dw]

I think I may have found an answer at
[url]http://www.aspfaqs.com/webtech/062899-1.shtml[/url]. Thanks, Aaron.

"dw" <cougarmana_NOSPAM@uncw.edu> wrote in message
news:%23ASkIR$GEHA.624@TK2MSFTNGP10.phx.gbl...

> Thanks, Aaron. However, we know how to do recordset paging; but returning
> 1100 records (even w/out the string concatenation) is slow. When we use
> maxrecords, it limits the entire recordset. What we're trying to do is to
> design the paging to just fetch the ones for that page, not the entire
> recordset. Thanks.
>
> "Aaron Bertrand [MVP]" <aaron@TRASHaspfaq.com> wrote in message
> news:ui6JxY%23GEHA.3556@TK2MSFTNGP11.phx.gbl...

> > Plenty of different approaches here:
> >
> > [url]http://www.aspfaq.com/2120[/url]
> >
> > Also, suggest doing the string operations on the name at the client,

where

> > you have to treat each iteration in the loop anyway. This should reduce

> the

> > strain on the actual SQL call...
> >
> > A
> >
> >
> >
> > "dw" <cougarmana_NOSPAM@uncw.edu> wrote in message
> > news:uMHsyB%23GEHA.2408@TK2MSFTNGP10.phx.gbl...

> > > Hello, all. We have a search page that can return many thousands of

> > records

> > > from a SQL Server 2000 database. We've noticed that it's slow --

mainly

> > b/c

> > > the stored procedure arranges the person's first, middle, last names

> into

> > > 'name' before returning the results. In addition, we're using

recordset

> > > paging (using Pagesize and Pagecount properties of the recordset).

Will

> we

> > > see a speed performance by using the Maxrecords property of the

> recordset?

> > > Are there any examples with recordset paging? Thanks.
> > >
> > >

> >
> >

>
>

[Aaron Bertrand [MVP]]

> Thanks, Aaron. However, we know how to do recordset paging; but returning

> 1100 records (even w/out the string concatenation) is slow. When we use
> maxrecords, it limits the entire recordset. What we're trying to do is to
> design the paging to just fetch the ones for that page, not the entire
> recordset. Thanks.

Did you notice that the article I pointed out offers several methods that
just fetch the ones for that page, not the entire recordset?