Post reply

An examination of bulk-logged recovery model

  • January 14, 2013 at 3:55 pm

    #1577107

    I re-created the statement(with a new database) and everything went OK!

    But I really can't understand why I'm n0t getting minimal logging in the code posted on the following url:

    This is the steps I'am doing

    1º Create database

    2 º Set Recovery Model to Bulk Logged

    3º Verify on sys.databases the recovery model

    4º Backup database (.bak)

    5º SELECT INTO + SHUTDOWN WITH NOWAIT

    6º DELETE MDF

    7ºRESTART SQL

    8º BACKUP TAIL LOG WITH NO_TRUNCATE

    9ºRESTORE DATABASE WITH NORecovery

    10º RESTORE LOG WITH RECOVERY(Error)

    11 º RESTORE LGO WITH RECOVERY,CONTINUE_AFTER_ERROR(OK)

    12 º SELECT * From SomeTable( AAAAAAAA)

    Code Used: http://pastebin.com/NZqkcKSY

    Thanks for your help

    GilaMonster (1/14/2013)

    Just go over it a couple times, make sure you are getting minimal logging. I ran that particular test a number of times, as did a friend and, while we got a variety of different errors, we did not get the table back intact after any of the tests.

  • January 18, 2016 at 4:41 am

    #1852468

    Great! So informative with detailed scenarios.

    Worth a read.

    One more disadvantage of Bulk logged recovery model is that if there are Bulk inserts, transaction log backup contains modified extents instead of individual log records (in case of Full recovery model). Hence the size of log backup increases tremendously.

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

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