jwcolby
jwcolby at colbyconsulting.com
Tue Apr 29 16:45:10 CDT 2008
That was indeed my original estimate. The PARSER was running at ~800 names / second. The UPDATE occurs after the parser finishes its thing., and is thus "in series with" (time wise) the parser. I just moved the VB.Net off to a more powerful machine and it is now running the parser at just over 3K records / second. I am in fact not parsing every record, I am actually processing ~80% of the records. Now I am off to see if I can figure out how to use threads. John W. Colby www.ColbyConsulting.com Robert L. Stewart wrote: > His original estimate was 50 hours. (not mine) > > But, he would have to do a bit of fancy coding in > SQL Server to use the same DLL he is using. That > bit of information was not in the first post. > > > > At 02:02 PM 4/29/2008, you wrote: >> Date: Tue, 29 Apr 2008 20:24:51 +0200 >> From: "Gustav Brock" <Gustav at cactus.dk> >> Subject: Re: [dba-VB] SQL VS VB >> To: <dba-vb at databaseadvisors.com> >> Message-ID: <s817842b.089 at cactus.dk> >> Content-Type: text/plain; charset=US-ASCII >> >> Hi Robert >> >> If the parser dll runs at about 800 records/s, 93 mio. records will >> need 33 hours as a minimum. Or? >> >> /gustav > > > _______________________________________________ > dba-VB mailing list > dba-VB at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-vb > http://www.databaseadvisors.com > >