Log Sequence Number

Why log sequence number gets broken in SQL server

June 29th, 2015 7:20am

Sorry, but we need some more information. What about your server, version, and the errorlog from your ERROR?

Why do you think, that your log sequence number get broken?

Kind regards,

Andreas


Free Windows Admin Tool Kit Click here and download it now
June 29th, 2015 9:06am

Why log sequence number gets broken in SQL server

Log sequence number is not broken its chain which links various pages having LSN stamped on it this link is broken. Go search online you would find the answer.

June 29th, 2015 9:29am

Hi Ranjit,

As described in this blog, sometimes, the Log Sequence Number(LSN) of the log is broken due to some user actions. In this case, you cannot take the successive log backups until a full or differential backup is taken.

The operations that will break the LSN chain are as follows:

Switching from the FULL or BULK_LOGGED recovery mode into the SIMPLE recovery mode
Reverting from a database snapshot
Taking Log Backup with NO_LOG option or with TRUNCATE_ONLY option.

Thanks,
Lydia

Free Windows Admin Tool Kit Click here and download it now
June 30th, 2015 2:31am

Thanks a ton Lydia 

July 1st, 2015 1:25am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics