Shamil Salakhetdinov
shamil at smsconsulting.spb.ru
Tue Apr 29 14:01:45 CDT 2008
<<< ...it is definitely going to be desirable to feed the update process off to a thread... >>> Hi John, I was lucky with multi-threaded batch updates' samples I posted here the day before yesterday - and the new tests show that batch updates in multi-threading environments result in MS SQL deadlocks: I should have thought about those issues before... Recap: forget batch updates - one of the scenarios of your task could be: - many readers; - many parsers; - but just one updater making batch updates, or many updaters but updating just one row in one cycle... HTH to save your time, Shamil -----Original Message----- From: dba-vb-bounces at databaseadvisors.com [mailto:dba-vb-bounces at databaseadvisors.com] On Behalf Of jwcolby Sent: Tuesday, April 29, 2008 3:31 AM To: Discussion concerning Visual Basic and related programming issues. Subject: Re: [dba-VB] vb.net - Updates We have ignition folks. I just updated the first 10K records in the database. I had to set the batch size to 100, as I was getting a timeout with a batch size as small as 1000 records. I haven't done any timings but it is definitely going to be desirable to feed the update process off to a thread if I can figure out how to do that. John W. Colby www.ColbyConsulting.com jwcolby wrote: > I THINK I have found my solution, called the SQLCommandBuilder. I found > reference to the command build saying how terrible it is, then a piece > of code that, in simple plain language, shows how to use it all, using > the simple objects I am already using. > > We shall see. _______________________________________________ dba-VB mailing list dba-VB at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-vb http://www.databaseadvisors.com