We've been using the new Get Database Measures command to take a look at what our application is actually doing, and plotting some of these metrics to our dashboard... for example, most frequently run queries. This particular query popped to the top, executing a few hundred times per minute.
And all it's doing is waiting for a relatively rare condition to happen (and a record to appear in this table). It might happen at most once or twice per day, maybe only once every few days, but when it happens it has to be dealt with immediately. It's such a waste to be constantly querying for a record that 99999 times out of 100000 won't exist. I feel like I'm missing an obvious solution. -- Jeffrey Kain [email protected] ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
