Send feedback on this topic.
Teradata.Client.Provider
Levels of Logging
.NET Data Provider for Teradata > Developer's Guide > Product Support, Troubleshooting and Error Messages > Troubleshooting > Levels of Logging

Debug Level

Debug level messages will contain data dumps of types internal to the provider, and other messages not covered by the other levels.  These messages will only be of value to the Teradata Global Support Staff. 

This level will also generate a tremendous amount of messages that will be written to the log file, and will have a significant negative impact to performance. 

Messages related to the Trace Internal Level will also be written to the log file.

Error Level

This level is used to log messages that deal with certain exceptions and other error conditions within the provider. 

These conditions include: 

Info Level

This level will log general informational messages valuable for determining state of system. This kind of message can gives hints/clues to where the system initial state was before an error or exception occurs.

Messages related to the Warning Level are also logged.

Trace External Level

This level will log entry and exit points of methods and properties of the ADO .NET Data Provider types implemented by the .NET Data Provider for Teradata.  Some of these types include TdConnection, TdCommand, TdParameter, etc…

Messages related to the Info Level are also logged.

Trace Internal Level

This level is used to capture tracing messages of methods or properties internal to the .NET Data Provider for Teradata.  The amount of data written to the log file will be tremendous, and the performance of the application will be greatly impacted.  This level will probably be of value to the Teradata Global Support Center.

This level will also log messages related to the Trace External Level.

Warning Level

The messages that are logged using this level will indicate a change of state of some component/class that could cause unexpected results in the system. These messages will also indicate where a problem might have initially started.  For example, this may include a database connection that has died, a transaction that did not complete successfully, or a command that was not executed on the Teradata Database System.

Messages related to the Error Level will also be logged.