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" <jbellnewsposts@.hotmail.com> wrote in message
news:AEFF783B-174E-493D-8CB1-83625E9D792F@.microsoft.com...[vbcol=seagreen]
> Hi Peter
> RESTORE HEADERONLY will give you the LSN range.
> John
> "Peter Reid" wrote:
Hi
You may want DBCC DBINFO, this is undocumented
See
http://www.sql-server-performance.co...ented_dbcc.asp
John
"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" <jbellnewsposts@.hotmail.com> wrote in message
> news:AEFF783B-174E-493D-8CB1-83625E9D792F@.microsoft.com...
>
>
|||Run
DBCC TraceOn(3604)-- to view the result in query analyzer.
DBCC DBInfo(<dbname>)
Regards
Amish
*** Sent via Developersdex http://www.codecomments.com ***
Showing posts with label john. Show all posts
Showing posts with label john. Show all posts
Friday, March 9, 2012
Expected LSN of a standby DB
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" <jbellnewsposts@.hotmail.com> wrote in message
news:AEFF783B-174E-493D-8CB1-83625E9D792F@.microsoft.com...[vbcol=seagreen]
> Hi Peter
> RESTORE HEADERONLY will give you the LSN range.
> John
> "Peter Reid" wrote:
>Hi
You may want DBCC DBINFO, this is undocumented
See
[url]http://www.sql-server-performance.com/ac_sql_server_2000_undocumented_dbcc.asp[/ur
l]
John
"Peter Reid" wrote:
> thanks john, but RESTORE HEADERONLY will give me the LSN range in the back
up
> file.
> I'm after the LSN a standby database is expecting next...
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:AEFF783B-174E-493D-8CB1-83625E9D792F@.microsoft.com...
>
>|||Run
DBCC TraceOn(3604)-- to view the result in query analyzer.
DBCC DBInfo(<dbname> )
Regards
Amish
*** Sent via Developersdex http://www.codecomments.com ***
file.
I'm after the LSN a standby database is expecting next...
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:AEFF783B-174E-493D-8CB1-83625E9D792F@.microsoft.com...[vbcol=seagreen]
> Hi Peter
> RESTORE HEADERONLY will give you the LSN range.
> John
> "Peter Reid" wrote:
>Hi
You may want DBCC DBINFO, this is undocumented
See
[url]http://www.sql-server-performance.com/ac_sql_server_2000_undocumented_dbcc.asp[/ur
l]
John
"Peter Reid" wrote:
> thanks john, but RESTORE HEADERONLY will give me the LSN range in the back
up
> file.
> I'm after the LSN a standby database is expecting next...
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:AEFF783B-174E-493D-8CB1-83625E9D792F@.microsoft.com...
>
>|||Run
DBCC TraceOn(3604)-- to view the result in query analyzer.
DBCC DBInfo(<dbname> )
Regards
Amish
*** Sent via Developersdex http://www.codecomments.com ***
Expected LSN of a standby DB
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" <jbellnewsposts@.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?
>>
>> ThanksHi
You may want DBCC DBINFO, this is undocumented
See
http://www.sql-server-performance.com/ac_sql_server_2000_undocumented_dbcc.asp
John
"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" <jbellnewsposts@.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
>
>
file.
I'm after the LSN a standby database is expecting next...
"John Bell" <jbellnewsposts@.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?
>>
>> ThanksHi
You may want DBCC DBINFO, this is undocumented
See
http://www.sql-server-performance.com/ac_sql_server_2000_undocumented_dbcc.asp
John
"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" <jbellnewsposts@.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
>
>
Subscribe to:
Posts (Atom)