Paul Hill <> wrote:
> Hi Peeps,
>
> I'm connecting to a SQL Server using server side cursors. If I do the
> following:
>
> SELECT * FROM big_table
>
> Followed by:
>
> RecordSet.FindFirst("keyfield = 123")
>
> What will actually happen? Will the client pull the entire dataset
> down and perform the search locally, or will the client & server do
> some magic and only send those records that match?
>
> I realise that this is far from ideal (should use a WHERE clause) but
> I'm looking into migrating a large legacy app to a SQL backend and
> this could be a good first step.
>
> I'm using ADO.
Sounds like you know that this process is wrong, yet you look for approval
because your "fixing" it. Sorry but you really need to get the refactoring
hat on and map out the proper path for C/S because when you ask for all the
rows from a big_table your stuck. :( ADO or ADO.NET it's just not built on
lots of rows in the object. Never has, and only going to ADO.NET in VS2005
will it work much better even though it still WRONG.
Use the Force.
Stephen Russell
DBA / Operations Developer
Memphis TN 38115
901.246-0159
http://spaces.msn.com/members/srussell/
--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.405 / Virus Database: 268.12.0/439 - Release Date: 9/6/2006
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
