August 13, 2007 at 12:35 pm
I have a client on SQL 2000 whose ODBC is configured to log long running queries to Query.log. I cannot access this file, however, and usually I can. I get a sharing violation when I try to open or move the file. It hasn't been written to in 2 days, and the server has been rebooted since then, and I tried to copy the file with SQL server and SQL agent stopped. Anyone know what to do? I need to review the file for an event that occurred.
It's stored in a default location, C:\documents and settings\administrator\local settings\temp\query.log although the path in the ODBC config shows it like C:\Docume~1\etc. if that matters. I had tried copying it from a command line.
August 14, 2007 at 6:48 am
Hi Mindy,
When we had similar problem, we must have disabled the logging at the ODBC connection, and after that we could read the log file. Give it a try...
-- Erik http://blog.rollback.hu
August 14, 2007 at 8:42 am
The ODBC connections set up have no logging enabled at this point that I can tell. I only saw the one in there that had been pointing to that file, and I had pointed it to a new file yesterday and have turned it off as well today. Still no love. I tried net file too to see if it would tell me anything but it didn't show the file.
August 14, 2007 at 8:58 am
Ok, I finally got it. I had to stop every service in the SQL Service Manager to gain access to it.
August 15, 2007 at 12:58 pm
Congrats! The explicit sense of 'sharing'.
One further note: 'C:\docume~1\...' is backwards commpatibility on directory naming in command lines to a time when each directory or file was limited to 8 characters left of the '.' - if you had two entries, say 'documents' and 'documentation', it's not clear to me whether you would have to use 'C:\docume~2\...' instead, since 'a' comes before 's'. But this is not strictly speaking a SQL Server matter, but windows/vista.
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply