Post reply

Transaction Logs

  • May 11, 2009 at 9:29 pm

    #209175

    Comments posted to this topic are about the item Transaction Logs

  • May 12, 2009 at 6:38 am

    #992804

    good, straightforward question. Always worth re-emphasising that backing up a log does not shrink it.

    ---------------------------------------------------------------------

  • May 12, 2009 at 7:24 am

    #992872

    Subtle difference in 'freeing up space' vs shrinking...nice question:

    http://msdn.microsoft.com/en-us/library/ms189085.aspx

    Truncation does not reduce the size of a physical log file. Reducing the physical size of a log file requires shrinking the file. For information about shrinking the size of the physical log file, see Shrinking the Transaction Log.

  • May 12, 2009 at 7:44 am

    #992916

    Wow, two complements in a row.

    Nice job, VM

  • May 12, 2009 at 8:48 am

    #993017

    That's odd, I checked these two answers:

    A DBCC SHRINKDATABASE statement is executed., An autoshrink operation occurs. , A DBCC SHRINKFILE statement referencing a log file is executed.

    And it told me I got it wrong. Hmmm...

  • May 12, 2009 at 8:53 am

    #993023

    Two or three? There were three correct answers to check.

  • May 12, 2009 at 1:58 pm

    #993260

    I must not have checked one of them then... I think I may have visually skipped over the autoshrink operation one. Makes more sense than a machine/web error.

  • May 13, 2009 at 1:18 am

    #993479

    Thanks for the compliments!

  • May 25, 2009 at 11:08 am

    #999715

    I disagree

    The question was:

    The size of the transaction log files are physically reduced when

    Physically reduced to me refers to the size of the file to the O.S. Then truncating the log would reduce phisically the log files, if there was available space.

    ________________
    DBA Cabuloso
    Lucas Benevides

Viewing 9 posts - 1 through 8 (of 8 total)

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