Use the ProtocolCapture connection string to capture Tabular Data Stream™ (TDS) packets exchanged between an ODBC application and the Server for debugging purposes. This property is enabled by specifying the capture file prefix.
ProtocolCapture takes effect immediately, so that TDS packets exchanged during connection establishment are written to a unique filename generated using the specified file prefix. TDS packets are written to the file for the duration of the connection. Use Ribo and other protocol translation tools to interpret the TDS capture files.
For example, to specify tds_capture as the TDS capture file prefix, type:
Driver=AdaptiveServerEnterprise;server=server1; port=port1;UID=sa;PWD=;ProtocolCapture=tds_capture;
The first connection generates tds_capture0.tds, the second connection generates tds_capture1.tds, and so forth.
Captured TDS protocol
data saved to a file contains sensitive user authentication information
and may contain confidential company or customer data. To protect
this confidential data from unauthorized or accidental disclosure,
the files containing captured data must be properly protected using file
permissions or encryption.
