On Feb 13, 2020, at 8:30 AM, Fennell, Brian <fenne...@radial.com<mailto:fenne...@radial.com>> wrote:
Try to figure out how you can do the whole thing in a single SQL statement, then just process the results one row at time. Well, based on his example code that’s exactly what he was doing. The only loop was processing the returned rows via $arraySelect->fetchrow_array() I am honestly with Geoffrey on this, I suspect something was broken on the DB itself and it was only coincidental that John’s script was running at the time the db became unresponsive. 1) this was a change in behavior without a change in code; the script had been running just fie for a long time. 2) barring the query returning enormous numbers of rows with a hugely inefficient query involving multiple remote database, etc , even a fairly minimal Oracle install can manage 4 queries per second (12K queries in 50 minutes) without becoming unresponsive, even if they do return tens or hundreds of thousands of rows. -- Bruce Johnson University of Arizona College of Pharmacy Information Technology Group Institutions do not have opinions, merely customs
