K
Keith Sudbury
Guest
Steps on soapbox... This is probably the thing I miss the most when switching between OE and other databases (SQL Server, PostgreSQL, Oracle, etc). The ability to see exactly what is going on in a database either right now or back in history. Making the statement caching safe and low impact would be a great start but we have a long way to go to catch up. Right now I am trying to track down a problem with excessive reads on a commonly used table. If it was a longer running query I could try and get a stack trace and find the problem code (or use statement caching). But this is a small enough table so reading the entire table only takes a few ms. Really there isn't an easy/low impact way in OE to find out what is reading the extra records. For other databases I just look at the query execution history (and/or turn on extended tracing for a certain table) and find the problem code pretty quickly. /end soapbox
Continue reading...
Continue reading...