August 11, 2011 at 1:38 am
Why bulk logged recovery model supports Logshipping?
Thanks
August 11, 2011 at 1:46 am
Bulk Logged Recovery model also supports point in time recovery ,provided the log file doent have a bulk operation.
August 11, 2011 at 2:44 am
This was removed by the editor as SPAM
August 11, 2011 at 2:52 am
forsqlserver (8/11/2011)
Why bulk logged recovery model supports Logshipping?
Very simple. You can able to take the log backup in this mode.
Muthukkumaran Kaliyamoorthy
https://www.sqlserverblogforum.com/
August 11, 2011 at 3:12 am
I have a issue..
If I do the bulk operations in this Primary database which is already logshipped and the bulk transactions will not be logged in the primary database transaction log then will logshipping be successful?
Thanks
August 11, 2011 at 3:26 am
This was removed by the editor as SPAM
August 11, 2011 at 4:37 pm
In the bulk-logging recovery model, transaction log backups contain all data pages that were modified as a result of the transactions in the transaction log backup. (Yes, the full modified page. Change a single bit? Back up the whole page.)
Bulk-logged transactions only store undo information in the log, not redo information, which is what keeps logging at a minimum. Having no redo information in the transaction log is why the log backups must contain all the changed pages. It also forces all bulk-logged transactions to be fully checkpointed (written to data files on disk) as part of the transaction. Without the right attention to setup and scenario, bulk-logged operations can be worse on performance than sticking with the full model. The only absolute benfit is a smaller transaction log file.
As a result of the log backup containing all the results of the transactions, restoring that log backup rolls the database recovery forward to the point at which the log backup was taken. Log shipping is simply restoring log backups to another server.
-Eddie
Eddie Wuerch
MCM: SQL
August 12, 2011 at 2:27 am
Eddie Wuerch (8/11/2011)
In the bulk-logging recovery model, transaction log backups contain all data pages that were modified as a result of the transactions in the transaction log backup. (Yes, the full modified page. Change a single bit? Back up the whole page.)
Only for minimally logged operations, and there are (fortunately) no minimally logged operations that change single bits. With the exception of one update , they're all inserts or index rebuilds.
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
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply