transaction log

Good day to everybody,

I have this problem once, but maybe i will encounter this again regarding the transaction log that I do not know why it grows bigger that it consume my harddisk space of 15gig althought my data file consume only 25mb How does it happen and why The only thing i do is to make a new temporary database, copy the tables inside on it and erase the old database whose transaction log is full, then bingo!!! I emptied my harddisk with the undesirable log file, then again make d'same database as the one I erase and copy again the tables at my temporary database created. 

Is there any other way I can empty my disk with that transaction log not by my way

I try to follow the message created by SQL that says something like 'BACK-UP THE DATABASE TO FREE THE TRANSACTION LOG' I do it but nothing happens, I can 't add any data anymore.

Thank you very much for any help




Answer this question

transaction log

  • TDi Develop

    You might have an open transaction on your database If you are using replication make sure the logreader agent is running. Also look at the BOL topic "Managing a Full Transaction Log"

    Philip


  • jbrunken

    If it is suitable consider changing your recovery model to simple (if not using replication).  Also, make sure you don't have any open transactions.  If you are using replication make sure the log reader agent is running.

    Philip

  • ucci

         How do I know that I have an open transaction in the database And where do i find that logreader agent
         I only have little background in MSSQL Server but I use MSSQL Server as my back-end database for my VISUAL FOXPRO apllication for almost 3 years now and that's the only problem i encountered so far.

        Thank you


  • .seb

    Run this command and see

    selecT * From sys.databases look for the

    log_reuse_wait_desc column and see why the log is getting full.

    IF transactions are not that important to you application you set your database to SIMPLE RECOVERY model, this process automatically truncates the log when chkpoint occurs

    log_reuse_wait_desc

    nvarchar(60)

    Description of reuse of transaction log space is currently waiting on one of the following:

    NOTHING

    CHECKPOINT

    LOG_BACKUP

    ACTIVE_BACKUP_OR_RESTORE

    ACTIVE_TRANSACTION

    DATABASE_MIRRORING

    REPLICATION

    DATABASE_SNAPSHOT_CREATION

    LOG_SCAN

    OTHER_TRANSIENT


  • transaction log