Re: SQL.LOG too big
From: Dinesh T.K (tkdinesh_at_nospam.mail.tkdinesh.com)
Date: 04/08/04
- Next message: Susan: "create a table prior to bcping data"
- Previous message: Huong: "RE: SQL.LOG too big"
- In reply to: Huong: "RE: SQL.LOG too big"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 9 Apr 2004 03:12:45 +0530
Amanda,
Since Iam unable to see the original message, Iam not sure what trace you
are talking about.Anyways, check out if ODBC trace is running (run
odbcad32.exe) and check on the 'tracing' tab.If so, stop it.More info:
PRB: ODBC Tracing to SQL.LOG Can Slow SQL Server or Consume All Disk Space
http://support.microsoft.com/default.aspx?scid=kb;en-us;268591
-- Dinesh SQL Server MVP -- -- SQL Server FAQ at http://www.tkdinesh.com "Huong" <anonymous@discussions.microsoft.com> wrote in message news:DBF560FD-5709-496A-A51A-9396B277CA32@microsoft.com... > Ilia, > Were you able to delete it? I tried to stop the trace and delete it, but unsucessful. It keeps saying "The process can't access the file because it is being used by another process." > Thanks, > Amanda
- Next message: Susan: "create a table prior to bcping data"
- Previous message: Huong: "RE: SQL.LOG too big"
- In reply to: Huong: "RE: SQL.LOG too big"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
