[Monetdb-developers] slow query log
Is there currently a syntax to log every incoming SQL query to a file?
I found options like:
1) ODBCDEBUG [1]
2) mapi_log(...) [2]
But is there something easy to capture all incoming query with their
timings; so a real slow queries log can be created?
In the Skyserver presentation [3] I see 'Query log' analysis; I'm really
interested in how this is realised. I would like to do an analysis on
all queries Mapserver generates by its GDAL/OGR layer, since I have
implemented this interface using ODBC (yes, I was too lazy to implement
a native connector) some logging would be possible, but not
concurrently, hence the file would be overwritten.
If nothing is in place, I'm happy to give it a try and implement it.
Stefan
[1] http://article.gmane.org/gmane.comp.db.monetdb.devel/1381
[2]
http://monetdb.cwi.nl/projects/monetdb/SQL/Documentation/Mapi-Function-Refer...
[3]
Stefan de Konink wrote:
Is there currently a syntax to log every incoming SQL query to a file?
I found options like: 1) ODBCDEBUG [1] 2) mapi_log(...) [2]
mclient links into the Linux history mechanism and logfile may help
But is there something easy to capture all incoming query with their timings; so a real slow queries log can be created?
If you run from an application, then it is easy to keep the log there. It includes valuable information about connections too.
In the Skyserver presentation [3] I see 'Query log' analysis; I'm really interested in how this is realised. I would like to do an analysis on
That was an analysis based on the query log maintained in MS SQL-server designed specifically for that application.
all queries Mapserver generates by its GDAL/OGR layer, since I have implemented this interface using ODBC (yes, I was too lazy to implement a native connector) some logging would be possible, but not concurrently, hence the file would be overwritten.
If nothing is in place, I'm happy to give it a try and implement it.
Current vision is that query logging is highly application specific and would lead to several knobs when put in place in the kernel. You can either keep the log outside the kernel, or sent the log record you want to retain to a table or even another site.
Stefan
[1] http://article.gmane.org/gmane.comp.db.monetdb.devel/1381 [2] http://monetdb.cwi.nl/projects/monetdb/SQL/Documentation/Mapi-Function-Refer... [3]
------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Monetdb-developers mailing list Monetdb-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-developers
On 21-10-2008 09:50:41 +0200, Martin Kersten wrote:
Stefan de Konink wrote:
Is there currently a syntax to log every incoming SQL query to a file?
I found options like: 1) ODBCDEBUG [1] 2) mapi_log(...) [2]
mclient links into the Linux history mechanism and logfile may help
That's only for the console input, isn't it?
But is there something easy to capture all incoming query with their timings; so a real slow queries log can be created?
If you run from an application, then it is easy to keep the log there. It includes valuable information about connections too.
what about the SQL server's PROFILE capabilities [1]? [1] http://monetdb.cwi.nl/projects/monetdb/SQL/Documentation/PROFILE-Statement.h...
participants (3)
-
Fabian Groffen
-
Martin Kersten
-
Stefan de Konink