December 19, 2005 at 11:33 am
Hi,
When you take a log backup in bulk-logged recovery mode, the extents modified by minimally logged bulk operations (identified by BCM pages) are copied to the transaction log. I have a question there.
Basically, at the time of restoring the database in case of a media failure, you restore the database and you start applying the transaction log. The question is whether the new extents are restored before any of the normal operations (non-bulk, that is) in the log are applied to the database, or after all the normal operations have been applied to the database. I think it should be before so that any non-bulk operation that attempts to register a change to any of these extents is prevented from doing so because these are in perfect condition. Please correct me if I am wrong.
Thanks,
Karim
December 20, 2005 at 3:31 am
A restore will apply your changes in the exact order in which they originally occurred. If restore worked in any other way, it would not be possible to do point-in-time recovery.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
December 20, 2005 at 9:07 am
I'm not sure it matters how the technical order of the restore goes. Once you start a log, it will complete as a single unit or work. It will work or not work, but there will be no half restores and you cannot do anything about that.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply