[SamThornton]

Gee, I don't think so. In fact, I didn't terminate the WHERE clause with ';'. Maybe that was the problem. Anywho, I'm leaving the thing alone for the time being–it's now taking about 5-6 minutes to run the process in question which I can live with. The other way, it was taking only a few seconds–real fast but real wrong.

[SamThornton]

Thanks for the quick response.

We're using v4.0.17 of mySQL. Unfortunately, the data is proprietary/confidential/financial, so can't supply copy.

Task scheduler has fired Job Agent several times on a couple of DB's since last post with no errors, so I'm assuming this is something I inadvertently did wrong.

Think problem may have been I was trying to use a timestamp field being >= current_date as a trigger and trying to monitor changes of just a few fields in a fairly huge, fairly static table in one database just to optimize the process. It optimized it all right, right out the window apparently. When I restored the the tables and ran just a plain-jane update process, things seemed to settle down. I'm running two update processes daily against two DBs and one against another DB every 6 hours, so this should be a good workout.

Thanks again. I'll report any glitches, if they occur.

[SamThornton]

Oops, this was accidentally submitted (was duplicate of above).

[Author]

Posts