January 4, 2012 at 6:29 am
SKYBVI (1/4/2012)
Is this question applicable for sql server 2005? I mean, will it work concurrently in sql server 2005?
Yes. The change first occurred in SQL Server 2005.
Paul White
SQLPerformance.com
SQLkiwi blog
@SQL_Kiwi
January 4, 2012 at 6:41 am
SQL Kiwi (1/4/2012)
SKYBVI (1/4/2012)
Is this question applicable for sql server 2005? I mean, will it work concurrently in sql server 2005?Yes. The change first occurred in SQL Server 2005.
That means we can put trans log for 24 hours continuous with full backup also scheduled within that 24 hours..
Won't there be discrepancy involved due to conflicting LSN numbers.?
Regards,
Skybvi.
Regards
Sushant Kumar
MCTS,MCP
January 4, 2012 at 6:49 am
No. You just need continuity in the LSN chain in the log backups. Remember you can restore logs right through a full backup without having to restore that full backup.
The LSN marker in the full backup just determines which is the next valid log backup if you start a restore chain from that full backup
---------------------------------------------------------------------
January 4, 2012 at 7:26 am
And to add to that, the only time that the LSN resets is when you change recovery mode. If you leave it in FULL mode, the LSN will be continuous throughout and as long as you have ALL of the transaction log backups, in theory you can restore from any full backup using tran logs to a particular point in time, even if additional full backups were taken after the one chosen.
January 24, 2012 at 2:01 am
Good question and interesting discussion.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
Viewing 5 posts - 16 through 19 (of 19 total)
You must be logged in to reply to this topic. Login to reply