StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>If you're accessing it via ODBC, you can turn on ODBC logging. It will slow things down a lot, though. And it won't work for any other data interface.</p> <p>Another thought is using Jet/ACE as a linked server in SQL Server, and then using SQL Profiler. But that's going to tell you the SQL that SQL Server processed, not what Jet/ACE processed. It may be sufficient for your purposes, but I don't think it would be a good diagnostic for Jet/ACE.</p> <p>EDIT:</p> <p>In a comment, the original poster has provided this rather crucial information:</p> <blockquote> <p>The application I am trying to monitor is compiled and at a customer's premises. I am trying to monitor what queries it is attempting against an MDB. I cannot modify the application. I am trying to do what SQL Profiler would do for a SQL Server.</p> </blockquote> <p>In that case, I think that you could do this:</p> <ol> <li><p>rename the original MDB to something else.</p></li> <li><p>use a SQL Server linked server to connect to the renamed MDB file.</p></li> <li><p>create a new MDB with the name of the original MDB and link to the SQL Server with ODBC.</p></li> </ol> <p>The result will be an MDB file that has the same tables in it as the original, but they are not local, but links to the SQL Server. In that case, all access will be going through the SQL Server and can be viewed with SQL Profiler.</p> <p>I don't have a clue what this would do to performance, or if it would break any of the data retrieval in the original app. If that app uses table-type recordsets or SEEK, then, yes, it will break. But this is the only way I can see to get logging.</p> <p>It shouldn't be surprising that there is no logging for Jet/ACE, given that there is no single server process managing access to the data store.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload