fn_dump_dblog

  • Hi All

    I have been trying to figure out what has caused a spike in the size of a particular log backup. '

    I am seeing entries for LOP_MODIFY_COLUMNS & LOP_MODIFY_ROW

    I found this in attempt to get an understanding...

    LOP_MODIFY_COLUMNS: Designates that a row was modified as the result of an Update command.

    LOP_MODIFY_ROW: Row modification as a result of an Update command.

    Am I missing something or are are the definitions exactly the same?

    I am seeing almost the exact same counts for LOP_INSERT_ROWS as LOP_MODIFY_COLUMNS.

    Are they related? I read somewhere that an update is a DELETE followed by an insert. Problem is, the counts for LOP_DELETE_ROWS is nowhere close to that of LOP_INSERT_ROWS & LOP_MODIFY_COLUMNS

    I used the following...

     

    SELECT Operation, partitionID ,count(*)Counts FROM fn_dump_dblog (NULL, NULL, N'DISK', 1, N'location',
    DEFAULT, DEFAULT, DEFAULT, DEFAULT, DEFAULT, DEFAULT, DEFAULT, DEFAULT, DEFAULT, DEFAULT, DEFAULT, DEFAULT, DEFAULT, DEFAULT,
    DEFAULT, DEFAULT, DEFAULT, DEFAULT, DEFAULT, DEFAULT, DEFAULT, DEFAULT, DEFAULT, DEFAULT, DEFAULT, DEFAULT, DEFAULT, DEFAULT,
    DEFAULT, DEFAULT, DEFAULT, DEFAULT, DEFAULT, DEFAULT, DEFAULT, DEFAULT, DEFAULT, DEFAULT, DEFAULT, DEFAULT, DEFAULT, DEFAULT,
    DEFAULT, DEFAULT, DEFAULT, DEFAULT, DEFAULT, DEFAULT, DEFAULT, DEFAULT, DEFAULT, DEFAULT, DEFAULT, DEFAULT, DEFAULT, DEFAULT,
    DEFAULT, DEFAULT, DEFAULT, DEFAULT, DEFAULT, DEFAULT, DEFAULT)

    group by Operation,partitionID
    order by Counts desc
    GO

     

    Thanks

  • Thanks for posting your issue and hopefully someone will answer soon.

    This is an automated bump to increase visibility of your question.

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

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