[dba-SQLServer]Large recordsets

Show me a human that can comprehend 50K rows at once, and I'll show you
either a liar or a savant.

If I were you I would flatly refuse this requirement. It's idiotic. Of
course in a reporting environment that's a different story, but in SQL
any form that returns 50K rows is IMO asinine.

My opinions about the requirements aside, do you mean precisely that you
are linked (i.e. ODBC) or are you using an ADP project? If the latter,
you might still be able to work in a paging scheme so the hit is
minimal. There are lots of examples of this sort of code around.
Basically you load a pageful and wait for the user to request another.

I've got a form-template that I call frmAlphabet, with 27 option buttons
on the header, all the letters plus "ALL". The AfterUpdate redefines the
RecordSource. In Access it writes a SELECT statement; in ADP it passes a
letter to a sproc containing a LIKE predicate. If you want it give me a
PM.

Arthur

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Martin
Reid
Sent: Sunday, November 23, 2003 12:03 PM
To: dba-sqlserver at databaseadvisors.com
Subject: [dba-SQLServer]Large recordsets


I have to return perhaps in access of 50,000 records for use in Access.
Linked to SQL Server 2000

What would be the fastest approach to take.

Comments appreciated.

Yeah I know the obvious, filter them first. But for the moment I am not
allowed. to.


Martin

_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com