Quantcast
Channel: Forum SQL Server Database Engine
Viewing all articles
Browse latest Browse all 15694

Minimally logged and point in time recovery .

$
0
0

In Minimally logged operation, If i change recovery model to bulk logged, and start bulk operation, after bulk operation if i insert 1 record to the same page on which bulk logged operation occurred, and now i take tlog backup, if i am right we can't rollback to prev state of insert of 1 record. so called PITR not possible in minimally logged.

======================= blogs

http://blogs.msdn.com/b/sqlserverstorageengine/archive/2008/02/05/bulk-logging-optimizations-minimal-logging.aspx

The only drawback of minimal logging is that it does not support point-in-time recovery. This is because during the transaction log backup, the state of the pages involved in the bulk import may have changed between the time bulk import was done and the transaction log back is initiated.  One can argue that we could possibly do point-in-time recovery to just before the bulk import had started but it is not supported. If this is of concern, you can do transaction log backup before/after bulk operations

from above does it mean when we opted for bulk logged recovery model, we can't use stopat in restore log even if we don't use bulk import operation?

means if i insert 1 record in page 1 and 2nd record in page 2, still it is not possible to use stopat in BL recovery model. Please clarify experts.

1 more question when we do bulk import , why sch-M locks needed when there's index on table (either clustered or Non-clustered index0?


Manish



Viewing all articles
Browse latest Browse all 15694

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>