[Previous entry: "Comments have been disabled from my weblog"] [Next entry: "A useful post on c.d.o.s about ADMIN_RESTRICTIONS_{listener_name}"]
Niall has clarified the ODBC trace issue
December 13th, 2004 by Pete
Post to del.icio.us
Post to Furl
I posted a blog entry last week about the many possible techniques that could be used to audit the SQL that is sent from a black box application to the database server. This is where the source code is not available for the application. I posted the entry "Auditing the SQL a black box application submits to the database" where I said, amongst other things:
"I am (almost?) certain OBDC trace can be used as well. I need to investigate this option - assuming ODBC is used of course"
Niall emailed me at the end of last week to let me know that ODBC trace is not useful in grabbing the SQL sent from an application that uses ODBC. Niall told me the following:
- It traces the ODBC calls and not the SQL itself - so you get lines like those listed at the end
- It is unbelievably slow, I mean truly, awfully slow
- I'm fairly sure that the original guy was using ADO which doesn't necessarily mean ODBC is involved anywhere
Thanks to Niall for the clarification on the ODBC issue.
For reference I also posted a second post on the subject of grabbing and auditing the SQL - This was called "Addendum to yesterdays auditing SQL from black box third party applications"
Finally Niall also made an additional post to the original thread on c.d.o.s today about ODBC that said:
"It is incredibly slow, and incredibly verbose. Those who bemoan the 'overhead' of timed_statistics=true or sql_trace ought to try it someday :("
