sql.log shrinking procedure

Question

Post reply

sql.log shrinking procedure

Branko Kovac

SSC Enthusiast

Points: 129
More actions
March 14, 2004 at 7:41 pm

#101917

Hi,
Could someone tell me what is the way to reduce size of sql.log file. File is not responding to backup, shrinkdb or shrinkfile. The sql.log is created and updated by SQL server in same directory as my user database file. If I execute command sp_helpfile the file is not listed as either db or log file.
Thanks.

Viewing 9 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic. Login to reply

TriggerMe SSChampion Points: 11752 More actions · Answer 1

How bout some thought into your question!

What do you mean by "File is not responding to backup, shrinkdb or shrinkfile"?

Tell us what actually happens when you attemt to execute one of the above methods.

Kindest Regards,

Branko Kovac SSC Enthusiast Points: 129 More actions · Answer 2

When I execute backup, shrinkdb or shrinkfile database file and log file both reduce in size but the sql.log file is unaffected by these commands.

Branko Kovac SSC Enthusiast Points: 129 More actions · Answer 3

I could rephrase the question into something like: Is there a command or procedure that can reduce size of sql.log file? I was experimenting using backup database and log file in enterprise manager. Also I used

shrinkdb

shrinkfile

that are suggested in manuals but the file did not reduce in size.

TriggerMe SSChampion Points: 11752 More actions · Answer 4

What is the sql.log file? Where is it found?

Kindest Regards,

Ken Klaft-80806 Say Hey Kid Points: 693 More actions · Answer 5

I can't say for certain that your sql.log file is unrelated to SQL Server, but I believe there's a default name of sql.log for ODBC trace files. Check any ODBC connections you may have set up on that box to see if you are tracing your sessions.

Also, if you're running Veritas on that machine you might want to check there. It sets up a MSDE instance and I believe it uses ODBC to communicate with it. There might be a switch on one if its DSNs.

Good luck.

Ken

Branko Kovac SSC Enthusiast Points: 129 More actions · Answer 6

Thanks a lot Ken. The problem was with ODBC tracing that was filling up the sql.log file.

Walter Gammell Newbie Points: 7 More actions · Answer 7

I have the same problem - this file is enormus in size, over 3.5 gig. How do you reduce this or even eliminate the tracing?

Branko Kovac SSC Enthusiast Points: 129 More actions · Answer 8

Go to Control Panel->Administrative Tools and double click on Data Sources (ODBC). Select "Tracing" tab and click button "Stop Tracing Now". Once you disable tracing you can delete the tracing file.