[dba-VB] SQL VS VB

Which is why it is going to take 50 hours instead of 2 or 3.


If you will give me an idea of what you are updating, I can send
you the SQL for the update.

"I know how to do it with a hammer, therefor, I will make everything
a nail."

Robert

At 12:00 PM 4/29/2008, you wrote:
>Date: Tue, 29 Apr 2008 11:43:45 -0400
>From: jwcolby <jwcolby at colbyconsulting.com>
>Subject: Re: [dba-VB] dba-VB Digest, Vol 54, Issue 28
>To: "Discussion concerning Visual Basic and related programming
>         issues."        <dba-vb at databaseadvisors.com>
>Message-ID: <48174231.4070501 at colbyconsulting.com>
>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>  > Yes, that is correct. He is ending up loading the records into memory.
>  > Then passing individual updates back for each row of data that he
>  > changed.
>
>Yes, and most records have updates.
>
>  > This method is not designed for doing large datasets like he is doing.
>  >
>  > It should be done on the SQL Server side.
>
>ROTFL.  That is a definite NSS.
>
>Unfortunately I am not a DBA and with the responses I get from the SQL
>group I am not even going there.  I can do this purely in VB.Net (it is
>cranking as we speak) so I will.
>
>  > Just what are you updating...the UPDATE statement you would use to
>  > do what you are doing.
>
>No idea.  I thought I could find out from the DA after the command
>builder was finished building the update statement but I am getting an
>error if I try to access the update property.
>
>John W. Colby