On 05/21/2014 02:05 PM, Ken Kixmoeller (ProFox) wrote: > On Wed, May 21, 2014 at 12:20 PM, Tracy Pearson <[email protected]>wrote: > >> Sounds like a network timeout to me. > > Thanks. The Im/Export processes hit the database pretty continually through > this, but if it is a network timeout, any ideas what to do about it?
My experience tells me that you shouldn't try to fix a hardware/network problem by coding around it. Let the client know they have a problem and they need to fix it. I'm guessing the big Import/Export routines have to have pretty exclusive access to the database so that no one updates stuff in the middle of your process. If that's true, why waste time trying to write a bunch of separate transactions to the network? Read from the network (perhaps even as a batch file, with COPY commands) and do the writing to the local drive, then load the result back up. That way you'll get local HDD speeds for the intensive processes, and you can use a bulk copy command to make one big write at the end of the process. If the bulk write fails, you still have the original copy and can retry without having to execute the process again. -- Ted Roche & Associates, LLC http://www.tedroche.com/ _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** 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.
