September 17, 2002 at 4:57 pm
I just want to move the SQL.LOG file to different drive ('cause of space) and configure DB Server to write to new drive.
Could some one please give me eact steps to do the above. I searched the server to reset the file I did not find settings for it.
Please help me. ASAP (Its space in the drive is getting close to Zero).
--Senthil
September 17, 2002 at 5:04 pm
I'm not really sure that SQL.LOG is. I think someone thought is was a transactionlog associated with a database. I'm not sure. Can you tell me what directory it is in? Have you tried to open it to determine what data is in it?
Gregory Larsen, DBA
If you looking for SQL Server Examples check out my website at http://www.geocities.com/sqlserverexamples
Gregory A. Larsen, MVP
September 17, 2002 at 5:44 pm
I don't think this is transaction log file.
When I go to the Properties of pubs db the log file is pubs_logs.ldf is stored in mssql\data\ directory, but the SQL.LOG file is created in C:\ directory. I haven't configured any parameter to C:\ directory where in installed SQL Server.
******Content of SQL.LOG File (Few Lines)****
sqlstp 5fc-154ENTER SQLAllocHandle
SQLSMALLINT 1 <SQL_HANDLE_ENV>
SQLHANDLE 00000000
SQLHANDLE * 00794818
sqlstp 5fc-154EXIT SQLAllocHandle with return code 0 (SQL_SUCCESS)
SQLSMALLINT 1 <SQL_HANDLE_ENV>
SQLHANDLE 00000000
SQLHANDLE * 0x00794818 ( 0x007b1768)
sqlstp 5fc-154ENTER SQLSetEnvAttr
SQLHENV 007B1768
SQLINTEGER 200 <SQL_ATTR_ODBC_VERSION>
SQLPOINTER 0x00000003
SQLINTEGER -6
September 18, 2002 at 4:48 am
SQL.LOG is the default name of the ODBC trace file. Open the control panel applet ODBC Data Sources. On the Tracing tab you will find the defined path and there you can change it and the name if something else may make better sense in the future to you.
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
September 18, 2002 at 10:14 am
Thanks a lot Antares686.
I change the directory in the Tracing folder On the ODBC DataSource Adminstrator Folder.
December 12, 2002 at 5:56 pm
This appears to have simple explanations but not simple solutions!
We have the same issue, our c:\sql.log grows until it kills the system (takes some time).
The logname can be changed with the odbcad32 utility but CANNOT BE SWITCHED OFF.
Our production server has the problem (was upgraded from 7 to 2000 sp2 and the services are run as domain\administrator) but a test server doesn't (fresh install of 2000 then sp2 run by local 'system').
ProcessExplorer from sysinternals shows very clearly that c:\sql.log is 'owned' or managed by the SQLAgent. When I switch off SQLagent the log stops accumulating (but I need the agent to run maintenance).
I can delete the file - stop the agent AND sqlserver and delete the file. Restarting both then kicks off a new file.
Everything points to the odbc manager (certainly the logfile name is stored in the odbc registry key) but the registry key is set to 0 (off) not 1 (on) and the odbc administrator does not show the logging to be started.
It looks as if the problem was caused by MS Query users (eg XL) doing queries with the base (office2000) odbc install but this does not hold up against the test system.
Does anyone have any ideas as to how to turn it off. The content of the log is of no use and doesn't even have a date/time stamp against each entry so is not of much use.
Would love some feedback.
December 12, 2002 at 8:12 pm
Check out this, http://support.microsoft.com/default.aspx?scid=KB;EN-US;q268591&
You are supposed to be able to stop tracing and it not log. Are you saying it is still logging after the fact? Try starting then stopping to see if the issue resolves. If not then let us know and see if anyone else can duplicate the problem as it needs to be reported but they will ask can it be duplicated.
December 12, 2002 at 8:55 pm
Yes, I agree you are supposed to switch off the trace, but we can't.
Prior to the upgrade (7 to 2k) there was no problem at all, the server ran for a long time (we've had it about three years) so if it was present then it would have caused a problem (the c:\ partition is only 4gigs with 1.5 free (it was set up by a Novell man!).
Since I couldn't switch logging off in odbcad32 I tried deleting the registry key.
I also tried changing the log file to \nul (doing a dir > \nul does it into thin air, like with unix \dev\nul) but while the registry key did update (after a complete restart (including system reboott)) it was still going to c:\sql.log (possibly because thats the default).
The file is currently 150megs and it was rebooted a 5pm last night (so its been running 22 hours, 7 of which are working).
I suspect senthil may also still have the problem because he's just changed the log to a different partition or drive. We've got plenty of space on the other drives but thats where the databases are.
James
December 13, 2002 at 7:23 am
You can turn on/off ODBC trace by changing the key in following registry HKEY_LOCAL_MACHINE\Software\ODBC\ODBC.ini\ODBC too. See http://support.microsoft.com/?kbid=274551.
December 16, 2002 at 9:35 am
da
Edited by - joachim.verhagen on 12/16/2002 09:37:07 AM
December 16, 2002 at 2:49 pm
Rats, I went and started a new thread while working through this one, sorry.
For completeness, there was another trace flag under HK_USERS. There was no other reference, eg to the location of the sql.log file so it had not stood out. I did a search for trace through the registry (previously I had searched for sql.log).
As of this morning (8:40am Sydney Aus) it is now (thankfully) dormant.
James
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply