SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Restore of the Database


Restore of the Database

Author
Message
Steve Jones
Steve Jones
SSC Guru
SSC Guru (148K reputation)SSC Guru (148K reputation)SSC Guru (148K reputation)SSC Guru (148K reputation)SSC Guru (148K reputation)SSC Guru (148K reputation)SSC Guru (148K reputation)SSC Guru (148K reputation)

Group: Administrators
Points: 148581 Visits: 19445
Why is verify history needed? I've never used this on the same server since backups are usually known quantities. It's on a DR server I might check since I don't have backup history.

Follow me on Twitter: @way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
Cliff Jones
Cliff Jones
SSCertifiable
SSCertifiable (5.2K reputation)SSCertifiable (5.2K reputation)SSCertifiable (5.2K reputation)SSCertifiable (5.2K reputation)SSCertifiable (5.2K reputation)SSCertifiable (5.2K reputation)SSCertifiable (5.2K reputation)SSCertifiable (5.2K reputation)

Group: General Forum Members
Points: 5229 Visits: 3648
The question probably should have said that RESTORE VERIFYONLY doesn't write to the msdb.dbo.restorehistory by default. But there is the LOADHISTORY parameter that will make it so.
igorg
igorg
SSC-Enthusiastic
SSC-Enthusiastic (143 reputation)SSC-Enthusiastic (143 reputation)SSC-Enthusiastic (143 reputation)SSC-Enthusiastic (143 reputation)SSC-Enthusiastic (143 reputation)SSC-Enthusiastic (143 reputation)SSC-Enthusiastic (143 reputation)SSC-Enthusiastic (143 reputation)

Group: General Forum Members
Points: 143 Visits: 13
I agree with Warren. In MSDN its clearly written that msdb.restorehistory contains one row for each restore operation.
For VERIFYONLY restore option column [restore_type] will contain 'V'
V = Verifyonly
Iggy-SQL
Iggy-SQL
Hall of Fame
Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)

Group: General Forum Members
Points: 3251 Visits: 440
igorg (1/21/2009)
I agree with Warren. In MSDN its clearly written that msdb.restorehistory contains one row for each restore operation.
For VERIFYONLY restore option column [restore_type] will contain 'V'
V = Verifyonly


RESTORE VERIFYONLY can write to history system table if you specify LOADHISTORY option. The question doesn't mention this at all, so the answer is No.


Urbis, an urban transformation company
Tom Thomson
Tom Thomson
One Orange Chip
One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)

Group: General Forum Members
Points: 26195 Visits: 12506
Iggy (1/21/2009)
igorg (1/21/2009)
I agree with Warren. In MSDN its clearly written that msdb.restorehistory contains one row for each restore operation.
For VERIFYONLY restore option column [restore_type] will contain 'V'
V = Verifyonly


RESTORE VERIFYONLY can write to history system table if you specify LOADHISTORY option. The question doesn't mention this at all, so the answer is No.


No. it's a stupid question and the correct answer "Only if LOADHISTORY" is specified isn't available.

Tom

Junior Galvão - MVP
Junior Galvão - MVP
Hall of Fame
Hall of Fame (3.7K reputation)Hall of Fame (3.7K reputation)Hall of Fame (3.7K reputation)Hall of Fame (3.7K reputation)Hall of Fame (3.7K reputation)Hall of Fame (3.7K reputation)Hall of Fame (3.7K reputation)Hall of Fame (3.7K reputation)

Group: General Forum Members
Points: 3716 Visits: 217
Hi,

Please check the correct answer!!!

The official Microsoft documentation informs the operation of verifyonly is written in the table.


To learn more visit: https://msdn.microsoft.com/en-us/library/ms187408.aspx
Jan Van der Eecken
Jan Van der Eecken
Hall of Fame
Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)

Group: General Forum Members
Points: 3279 Visits: 6497
Junior Galvão - MVP (5/9/2016)
Hi,

Please check the correct answer!!!

The official Microsoft documentation informs the operation of verifyonly is written in the table.


To learn more visit: https://msdn.microsoft.com/en-us/library/ms187408.aspx


Uhmmm... This question is 6 years old w00t

--------------------------------------------------------------------------
A little knowledge is a dangerous thing (Alexander Pope)

In order for us to help you as efficiently as possible, please read this before posting (courtesy of Jeff Moden)
Tom Thomson
Tom Thomson
One Orange Chip
One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)

Group: General Forum Members
Points: 26195 Visits: 12506
Jan Van der Eecken (5/9/2016)
Junior Galvão - MVP (5/9/2016)
Hi,

Please check the correct answer!!!

The official Microsoft documentation informs the operation of verifyonly is written in the table.


To learn more visit: https://msdn.microsoft.com/en-us/library/ms187408.aspx


Uhmmm... This question is 6 years old w00t

So it's been standing there wrong - uncorrected - for 7 (not 6) years despite the error having been pointed out 7 years ago. How many people have looked at it and been misled during those 7 years? Do we want SQLServerCentral to carry on misleading people for ever, or should people who spot the uncorrected error comment on it in the hope that it may be fixed even at this late date so that it won't mislead people in the future? If that's a forlorn hope, what does that say about the site? And if you think people shouldn't comment, what does that say about you?

Tom

Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search