Debug queries using OpenBD's slow log feature

Have you ever wondered what queries your CFML application is making? Or how long each query is taking? Or even better, how would you like to log queries that take a given amount of time to execute?

The popular MySQL database has always had the very handy 'slow log' feature, where by it can log long running queries that execute over a given timeout threshold. Extremely useful for debugging and spotting long running queries.

However, not all databases have this feature, and more importantly, they don't give you a full view from the point of view of your CFML application. With that in mind, OpenBD introduces the Slow Log feature to your CFML querying functionility.

Any query run via CFQUERY, CFSTOREDPROC, or as a background thread, can be traced using the new "slow log" functionality. You can determine the length the query took, the SQL statement or stored-procedure name, and the precise location within your application the query originated from.

This is logged into a rotating log file, allowing you to log every query made, or only ones that exceed a timeout value. This can be used irrespective of the backend database, and takes into account all network delays associated with making the query.

For full details see: OpenBD Slow Log Wiki

This is now available in our nightly build and will be in our upcoming official release very soon.