what needs to be done for tranactional log is full on sql server for next time

  • hey,

    recently one of the database transnational log is full. we are revived the error so i have took log backup and shrunk the database after taking the backup.

    in the the future What needs to be done so that this does not happen again?

    can any one suggest

  • What you did was actually improper way to manage log if its is Production server. because it can break the log chain.

    This link can help you better http://www.sqlservercentral.com/stairway/73776/

    -------Bhuvnesh----------
    I work only to learn Sql Server...though my company pays me for getting their stuff done;-)

  • Basicly: Allow the LOG file to grow and keep enough free space on disk.

    Try to figure out why the LOG has been growing this big and see if it can happen again. Ask the business when they execute actions that need the LOG to grow extensively. Also look at your own maintenance actions (like index maintenance).

    If the log repeatedly grows to a specific size, don't shrink the LOG file to a smaller size.

    ** Don't mistake the ‘stupidity of the crowd’ for the ‘wisdom of the group’! **
  • http://www.sqlservercentral.com/articles/Transaction+Logs/72488/

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • Why is my log full?[/url]

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

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

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