Client Side Cache ?? (was Re: How to limit # of rows ..)
From: Jim Holt <jim_holt_at_email.sps.mot.com>
Date: 1996/02/28
Message-ID: <jim_holt-2802960806080001_at_jolt.sps.mot.com>#1/1
Date: 1996/02/28
Message-ID: <jim_holt-2802960806080001_at_jolt.sps.mot.com>#1/1
In article <3131EFFA.75C0_at_leadingbits.via.at>, Dieter Oberkofler <dtr_at_leadingbits.via.at> wrote:
> Jason Lincoln wrote:
<snip>
> > >> Does anybody know if there is a way to limit the number of records
> > >> returned by a SELECT statement? I have a large ODBC database
> >
I am new to SQL Server, and this thread has me a little confused.
Why should the number of rows returned be an issue ? Is this a memory issue on the client ? Isn't this type of problem handled by something like a cursor ?
Just curious...
-jh
Received on Wed Feb 28 1996 - 00:00:00 CET