[dba-SQLServer]Large recordsets

Run Query Analyzer to check the execution plan for each of the procedures that you ARE running.  It is possible that you may need to add/remove indexes from tables in order to optimze your return.


-- 
-Francisco



Martin Reid wrote:

>Sorry
>
>50 thousand records
>
>Using an unbound Access app and I need to bring all 50000 at one go to the
>form. I cannot change this as all records have to be available.
>
>Takes 3 seconds to open and populate the form using a number of stored
>procedures and recordsets. I was wondering if there was a faster way to do
>this.
>
>
>Martin
>
>
>----- Original Message ----- 
>From: "Erwin Craps" <Erwin.Craps at ithelps.be>
>To: <dba-sqlserver at databaseadvisors.com>
>Sent: Sunday, November 23, 2003 8:31 PM
>Subject: RE: [dba-SQLServer]Large recordsets
>
>
>  
>
>>Martin,
>>
>>Your question is not very clear to me.
>>What is it that you want to do?
>>I don't see what the prob is with "only" 50.000 records.
>>
>>Erwin
>>
>>-----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 9: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
>>
>>    
>>