![]() ![]() Jet Profiler is designed for MySQL DBAs and application developers who need to understand how their databases are performing under any given workload or environment configuration. Its user interface provides a summary of the collected data and allows you to dig deeper into queries of interest. The tool records data about each query, such as timing data and system information. It allows you to monitor and analyze live database queries, and it has a built-in benchmarking tool that will show you how changes to your configuration affect query performance. 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.Jet Profiler for MySQL is a real-time query performance and diagnostics tool for the MySQL database server. But this is the only way I can see to get logging. If that app uses table-type recordsets or SEEK, then, yes, it will break. 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. ![]() In that case, all access will be going through the SQL Server and can be viewed with SQL Profiler. 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. Use a SQL Server linked server to connect to the renamed MDB file.Ĭreate a new MDB with the name of the original MDB and link to the SQL Server with ODBC. Rename the original MDB to something else. In that case, I think that you could do this: In a comment, the original poster has provided this rather crucial information: It may be sufficient for your purposes, but I don't think it would be a good diagnostic for Jet/ACE. But that's going to tell you the SQL that SQL Server processed, not what Jet/ACE processed. And it won't work for any other data interface.Īnother thought is using Jet/ACE as a linked server in SQL Server, and then using SQL Profiler. If you're accessing it via ODBC, you can turn on ODBC logging. The tool ShowplanCapturer (see, to download also in english) can be also helpful for you. UPDATED 2: For more recent version of Access (like Access 2007) use key like HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\12.0\Access Connectivity Engine\Engines. In my practice JETSHOWPLAN gives perfect information for me. If this output will be not enough for you you can additionally use TraceSQLMode and TraceODBCAPI from HKEY_LOCAL_MACHINE\Software\Microsoft\Jet\4.0\Engines\ODBC. This key described for example in, and corresponds to allow trace OLE DB queries. UPDATED: Because use use DAO (Jet Engine) and OLE DB from VB I recommend you create JETSHOWPLAN regisry key with the "ON" value under HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\JET\4.0\Engines\Debug (Debug subkey you have to create). MDB is a file without any active components, so the tracing can makes not MDB itself, but the DB interface only. I can continue, but before all you should exactly define which interface you use to access MDB. If you use OLEDB to access MDB from SQL Server you can use DBCC TRACEON (see ). There are different tracing settings which you can configure in HKEY_LOCAL_MACHINE\Software\Microsoft\Jet\4.0\Engines\ODBC. ![]() The answer depend on the technology used from the client which use MDB.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |