"John Bell" <jbellnewspo***@hotmail.com> wrote in message
news:AEFF783B-174E-493D-8CB1-83625E9D792F@microsoft.com...
> Hi Peter
>
> RESTORE HEADERONLY will give you the LSN range.
>
> John
>
> "Peter Reid" wrote:
>
>> Is it possible to query the next expected LSN from a DB in
>> recovery/standby?
>>
>> I know that if you try to restore a log backup out of sequence, SQL
>> Server
>> throws error #4326 which will tell you the LSN you just tried to restore
>> and
>> the expected one, but is it possible to get this info without having to
>> attempt a log restore?
>>
>> Thanks

"Peter Reid" wrote:

> thanks john, but RESTORE HEADERONLY will give me the LSN range in the backup
> file.
> I'm after the LSN a standby database is expecting next...
>
>
>
> "John Bell" <jbellnewspo***@hotmail.com> wrote in message
> news:AEFF783B-174E-493D-8CB1-83625E9D792F@microsoft.com...
> > Hi Peter
> >
> > RESTORE HEADERONLY will give you the LSN range.
> >
> > John
> >
> > "Peter Reid" wrote:
> >
> >> Is it possible to query the next expected LSN from a DB in
> >> recovery/standby?
> >>
> >> I know that if you try to restore a log backup out of sequence, SQL
> >> Server
> >> throws error #4326 which will tell you the LSN you just tried to restore
> >> and
> >> the expected one, but is it possible to get this info without having to
> >> attempt a log restore?
> >>
> >> Thanks
>
>
>