Post reply

SQL Server Logs

  • February 28, 2005 at 9:11 am

    #92465

    Wondered if you could help...

    We have a cluster SQL server and have noticed to our horror that the Current SQL Server Log has clocked up over 14Gb's. In comparison, the maximum Archive log is 5.7Gb.

    The question we would like to raise is 'Is there anyway of controlling the size of the log file'?

    It just takes an age to view this size of log...

  • March 1, 2005 at 7:45 am

    #544607

    You can periodically cycle the logs without rebooting. sp_cycle_errorlog or something like that will work. I had a server that never went down and we had the same issue, so we cycled them every week.

    Follow me on Twitter: http://www.twitter.com/way0utwest
    Forum Etiquette: How to post data/code on a forum to get the best help
    My Blog: www.voiceofthedba.com

  • March 1, 2005 at 10:04 am

    #544643

    To cut directly to the chase:

    use master

    go

    dbcc errorlog

    go

    checkpoint

    go

    It works well as a scheduled task.

    RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."

  • March 2, 2005 at 1:28 am

    #544783

    Thanks rudy

    Brilliant - I'll shall apply a scheduled task to all our SQL Servers on a period base

  • March 2, 2005 at 2:34 am

    #544799

    We've got something along the lines of what Steve is suggesting. However, the stored proc that does this renames the log file so it doesn't get automatically removed.

     

    --------------------
    Colt 45 - the original point and click interface

Viewing 5 posts - 1 through 4 (of 4 total)

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