On Tue, Jul 29, 2014 at 7:06 PM, Sytze de Boer <[email protected]> wrote:
> Everyone, thank you for your help. > My old routine took point 419 seconds, the new routine point 350 > > This leads to my next question > Which of the two methods is *better* (i.e. used by experts) > 1 Update, set etc > 2 Scan/endscan with replace > 3 set a relation and replace all > > By *better*, I'm referring to speed and record/file locking. > > ------------------------------ Better should consider growth over time as well. I have made a decent living tweaking developer code against the back end because a hundred rows acts this way by 100 thousand acts differently. In this situation you may find that you can do your sum statement on the entire table with the where clause keeping only the few needed within the dataset, then join back to that in your update statement. Putting functionality to sum another table by a single row's params in this table receiving the update is not usually a good idea. -- Stephen Russell Sr. Analyst Ring Container Technology Oakland TN 901.246-0159 cell --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html --- _______________________________________________ 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/cajidmyjse6xtzux+mnge6gczerfivovnza_uvrq__yf6vxy...@mail.gmail.com ** 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.
