Transaction Log Backup-----Emergency

  • Hi all,

    I have two log files to my database one of 100MB and second of 1GB.

    I scheduled backup of transaction logs for every 2 hours and it used to be only 50MB or some time 200MB.

    But today it is something horrible.

    I see the backup of transaction log as 1.2 GB or 1.3 GB for every 2 hours.

    DBCC SELPERF(logspace) shows the rate on how it is increaing the logfile.

    Anyone please help me.....its really very urgent

    Will be verymuch thankful to you.........please

  • Did you take a look on the activity that is going on the server.

    Refer : http://www.sqlservercentral.com/redirect/articles/67120/

    [font="Verdana"]Thanks
    Chandra Mohan[/font]

  • A large logfile means something is running on your database. Did the full backup ran properly?

    Check databaseactivity: Is the logfile still growing? There must be a process which is blowing up your logfile.

    Wilfred
    The best things in life are the simple things

  • seems to me like there is huge data insert activity happening?

    Or are you running maintainance plans(index rebuilds?)

    for the moment, take backup of the log more frequently.

    later when there is less activity on the system, you might want to shrink logs for once.



    Pradeep Singh

  • Part of all your replies helped me to analyse the issue.

    There is an update statement running since yesterday.

    Thank You to all

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

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