Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
The Sql.log file may consume all disk space and cause SQL Server to run slowly when you turn on ODBC Tracing
Article ID: 268591 - View products that this article applies to.
This article was previously published under Q268591
Open Database Connectivity (ODBC) Tracing can be used to trace calls to ODBC functions from ODBC applications. The ODBC Driver Manager can trace calls continuously or for one connection only, can perform tracing dynamically, or can allow tracing to be performed by a custom trace .dll file. ODBC Tracing stores information in a file on the local hard drive. By default, the file name is "SQL.LOG" and its physical location is the root of the system partition (that is, where the %windows% directory resides. For example C:\sql.log). The file location and name can be edited in the ODBC Data Source Administrator.
The user needs to be aware that having ODBC Tracing turned on can result in two problems:
To turn off ODBC Tracing and remove the associated file, follow these steps:
For additional information on ODBC Tracing and SQL Server, click the article numbers below to view the articles in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/140895/EN-US/ )INF: Diagnostic Tips for the Microsoft SQL Server ODBC Driver
(http://support.microsoft.com/kb/139655/EN-US/ )INF: Tracing SQL Generated by MS SQL Server ODBC Driver
(http://support.microsoft.com/kb/248704/EN-US/ )Open Database Connectivity Performance Slow When Tracing Enabled
Article ID: 268591 - Last Review: February 22, 2007 - Revision: 4.3