Post reply

transaction log grows too large

  • March 31, 2006 at 2:37 pm

    #168900

    I am trying to upgrade a database from 1 version of our product to another.  During the upgrade process, the database scripts, every column in the database to unicode.  Against a large database, transaction log is growing very fast and is growing infinitely. 

    Is there any way, I can disable writing to transaction log?

     

    Thanks

    Haritha

     

  • March 31, 2006 at 4:06 pm

    #630248

    With few execptions (bulk inserts in the bulk-logged recovery model), all database changes are written to the log first.  Later, another process captures those changes that have been committed and writes them to the actual data files.  The answer to your question is that you can't disable log writes.

    If you have control over the upgrade scripts, then split the work into smaller batches and occasionally back up the transaction log between them to free up space.  If the whole thing happens in a single transaction, then it must all be written to the log before any of it can be committed.

    -Eddie

    Eddie Wuerch
    MCM: SQL

Viewing 2 posts - 1 through 1 (of 1 total)

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