This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

How to turn down logging?

Last night my LiteSpeed for SQL Server generated over 340GB of log files and totally filled one drive on my production SQL Server.  Luckily is was not the C: drive.

When I go into the Options screen of the LiteSpeed console, I see Logging Level is set to "Errors only" and since my LiteSpeed has been running without issue for several months, I can't imagine there are so many errors that it would generate hundreds of gigbytes of log files.  There must be another place that has logging cranked up.  Does anyone have a recommendation on where I could check to see where LiteSpeed has a logging configuration that's generating so many files?  I feel foolish opening up a support ticket for such a trivial thing but it has the potential to cause real problems.

Any help appreciated.

Ken

  • Hello Ken,

    The logging set under "options" in the LS console are for the actions taken by the console and are recorded in the application event logs.

    The logging you are interested in is engine logging and can be set either per job or globally per server.

    I would check the per server settings first by looking here.

    Right click the SQL instance in the Litespeed console and select "Support | Litespeed logging"

    Then deselect any option checked marked here or you may wish to select "delete log file on success".

     If you wish to see if your engine logging is setup per job. Check your job's script for any lines such as the below.

    @logging = 2,

    It is safe to remove this line if needed.

    You can also review what is set under "advanced options | logging level" for that job.

    EXAMPLE:

    Hope that helps,

    -Ben-

  • Thank you, thank you, thank you.  I was looking at the jobs within Management Studio, the options within the LiteSpeed Console, and even the registry entries for LiteSpeed.  I would never have thought to look at the properties of the servers within the LiteSpeed itself. 

    All logging has been turned off at this time.

    Ken