Stairway to Transaction Log Management in SQL Server, Level 6: Managing the Log in BULK_LOGGED Recovery Model

  • Comments posted to this topic are about the item Stairway to Transaction Log Management in SQL Server, Level 6: Managing the Log in BULK_LOGGED Recovery Model

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • I'm sure I've said this before, but I don't think the advantages of using BULK LOGGED mode are worth the potential risks. If the data is critical enough that the database is normally in FULL recovery, then IMHO it's too critical to risk losing a chunk of it. Conversely, if it ISN'T that critical, you might as well run the database in SIMPLE recovery and not bother with logs at all! Of course, this is purely an opinion, your mileage may vary, etc... 🙂

  • Hi, in your post, you can find the data in the [Log Record] of fn_DBLog feedback.

    but the string is too long.

    /**

    create table c (name char(5))

    insert into c select 'wison'

    **/

    the [Log Record] of fn_DBLog related to the [LOP_INSERT_ROWS] is :

    0x00003E0015000000D00000000100020063020000000002019F000000010000001E00000015000000D00000000F000001000010000000000100000000410003000C00000014004200100009007769736F6E0100000101000C00009211550000000102000402030004

    how can i analysis it?

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

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