如何从服务器端查看MDA程序的数据库查询语句并复现报表？

Absolutely—you can absolutely capture the exact SQL queries that MDA sends to your database, and here are the most reliable ways to do it depending on your database system:

1. Enable Database Query Logging (Most Direct Method) #

The exact steps depend on what database your server is running:

For MySQL/MariaDB #

• Log into your database server as an administrative user.
• Temporarily enable the general query log (this resets on server restart unless you update the config file):

  SET GLOBAL general_log = 'ON';
  SET GLOBAL general_log_file = '/var/log/mysql/mda_queries.log'; -- Adjust the file path to match your server setup
  

• Run the MDA report you want to replicate, then disable the log to avoid unnecessary disk usage:

  SET GLOBAL general_log = 'OFF';
  

• Open the log file—you’ll find every query MDA sent, including the exact one generating your target report.

For SQL Server #

• Use either SQL Server Profiler or Extended Events to capture queries:
  • SQL Server Profiler: Create a new trace, select the SQL:BatchCompleted and RPC:Completed events, then filter by the application name (look for "MDA" or the program’s unique identifier).
  • Extended Events: Run this script to create a dedicated session for capturing MDA’s queries:

    CREATE EVENT SESSION CaptureMDAQueries ON SERVER 
    ADD EVENT sqlserver.sql_statement_completed(
        ACTION(sqlserver.session_id, sqlserver.sql_text)
        WHERE sqlserver.client_app_name = 'MDA' -- Tweak this if your MDA uses a different app name
    )
    ADD TARGET package0.event_file(SET filename=N'MDAQueries.xel')
    WITH (STARTUP_STATE=OFF);
    

• Start the session, run your MDA report, stop the session, then analyze the .xel file in SQL Server Management Studio to extract the query.

For PostgreSQL #

• Edit your postgresql.conf file to enable full query logging:

  log_statement = 'all'
  log_filename = 'mda_queries.log'
  log_directory = '/var/log/postgresql/' -- Adjust to your server's log path
  

• Restart PostgreSQL, run the MDA report, then revert the setting (set log_statement = 'none' or its default value) to stop logging.
• Check the generated log file for the exact SQL query.

2. Use a Database Proxy Tool #

If you don’t want to modify server-side logging settings, tools like ProxySQL (for MySQL) or pgBouncer (for PostgreSQL) can act as an intermediary between MDA and the database. Configure the proxy to log all incoming queries, point MDA to the proxy instead of the direct database, then run your report to capture the SQL.

3. Check for MDA's Built-in Logging #

Some applications hide debug or query logging options in their admin panels or config files. Dig through MDA’s settings (look for .ini, .conf, or settings.xml files) to see if there’s an option to enable "database query logging" or "debug mode." This is the cleanest method if available, as it only logs MDA’s traffic without extra server noise.

Key Notes #

• You’ll need server admin or database owner permissions for most of these methods.
• Always disable logging after capturing your target query—leaving it active can slow down your server and fill disk space over time.
• Once you have the SQL, you can use Excel’s Power Query (Data > Get Data > From Database) to run the query and replicate the report directly in Excel.

内容的提问来源于stack exchange，提问作者Warric Ritchie