Requests tracing information that logs transaction records to an external file.
| Valid in: | SAS/ACCESS LIBNAME statement |
|---|---|
| Category: | Data Set Control |
| Default: | none |
| Interactions: | The DRIVER_TRACEFILE= option is required when you specify the DRIVER_TRACE= LIBNAME option. |
| (Optional) You can control trace log formatting with the DRIVER_TRACEOPTIONS= LIBNAME option. | |
| Data source: | Google BigQuery, Hadoop, JDBC, Spark |
| Notes: | Support for this option was added in the August 2019 release of SAS/ACCESS. |
| Support for Hadoop, JDBC, and Spark was added in SAS 9.4M9. | |
| This option applies only when submitting FedSQL and DS2 programs in PROC FEDSQL and PROC DS2. | |
| See: | DRIVER_TRACEFILE= LIBNAME option, DRIVER_TRACEOPTIONS= LIBNAME option |
Table of Contents
specifies the level of information that is recorded in the log file.
You can specify multiple
values within parentheses, separated by a comma. For example, you
can specify SQL and DRIVER values as DRIVER_TRACE=(SQL,
DRIVER).
Here are the possible values:
| ALL | records the information from all of the possible values of DRIVER_TRACE=. |
| SQL | records the SQL statements that are sent to the DBMS in the trace log. |
| DRIVER | records driver-specific information in the trace log. |
The log file for the DRIVER_TRACE= option is specified by the DRIVER_TRACEFILE= LIBNAME option.
The DRIVER_TRACE=, DRIVER_TRACEFILE=, and DRIVER_TRACEOPTION= LIBNAME options can be used to enable driver tracing when working with PROC FEDSQL and PROC DS2. These options are typically used with the guidance of SAS Technical Support to assist in diagnosing complex or advanced issues.
To generate tracing in other contexts, see SASTRACE= SAS System Option.