Re: VB App fails when log reaches 65536
- From: DanS <t.h.i.s.n.t.h.a.t@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 18 Mar 2009 23:16:36 +0000 (UTC)
=?Utf-8?B?Q3Jvd25NYW4=?= <CrownMan@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
news:6C27011E-86F3-461E-BA12-90908DBD327B@xxxxxxxxxxxxx:
see, the SQL Server where we are trying to query against contains over
5 million records, but it is 7 years old...a pentium class old server
that does not perform very well. So...the app creates client side
cursors, goes on to do a lot of processing and finally, it begins to
spit out records and writes to the log. Well, it takes like 20
minutes to process the query...and when it finally does....it quits
at that number...
Are you sure it's creating a client-side cursor ?
I haven't done a database app in a while, but IIRC, when a client-side
cursor is used, the db server does nothing except hand off the entire db to
the client program and then the client app generates the query locally.
That means that if the query resultant set is let's say 10,000 records, the
client still gets handed all 5 million records over the network, which
could be a problem with a slow connection.
To the contrary, with a server-side cursor, the SQLServer will run the
query and hand over only the 10,000 records to the client.
Maybe it's time to spend $200 to update the SQL server's MB,CPU and RAM.
You can get a motherboard, near 3Ghz dual core AMD CPU, and 2 Gigs of RAM
for that much moolah.
.
- Follow-Ups:
- Re: VB App fails when log reaches 65536
- From: Al Reid
- Re: VB App fails when log reaches 65536
- References:
- VB App fails when log reaches 65536
- From: CrownMan
- Re: VB App fails when log reaches 65536
- From: Nobody
- Re: VB App fails when log reaches 65536
- From: CrownMan
- VB App fails when log reaches 65536
- Prev by Date: Re: Active X and Vista
- Next by Date: Re: VB App fails when log reaches 65536
- Previous by thread: Re: VB App fails when log reaches 65536
- Next by thread: Re: VB App fails when log reaches 65536
- Index(es):
Relevant Pages
|