InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comWed, 19 Jun 2013 15:46:14 GMT20http://www.sqlservercentral.com/Forums/Topic640366-1461-1.aspx[quote][b]Iggy (1/21/2009)[/b][hr][quote][b]igorg (1/21/2009)[/b][hr]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[/quote]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.[/quote]No. it's a stupid question and the correct answer "Only if LOADHISTORY" is specified isn't available. Tue, 23 Jun 2009 08:26:52 GMTL' Eomot Inverséhttp://www.sqlservercentral.com/Forums/Topic640366-1461-1.aspx[quote][b]igorg (1/21/2009)[/b][hr]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[/quote]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.Wed, 21 Jan 2009 15:23:46 GMTIggy-SQLhttp://www.sqlservercentral.com/Forums/Topic640366-1461-1.aspxI 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 = VerifyonlyWed, 21 Jan 2009 13:14:19 GMTigorghttp://www.sqlservercentral.com/Forums/Topic640366-1461-1.aspxThe 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.Wed, 21 Jan 2009 07:48:23 GMTCliff Joneshttp://www.sqlservercentral.com/Forums/Topic640366-1461-1.aspxWhy 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.Wed, 21 Jan 2009 07:23:45 GMTSteve Jones - SSC Editorhttp://www.sqlservercentral.com/Forums/Topic640366-1461-1.aspx[quote][b]Steven Cameron (1/21/2009)[/b][hr]I got the question wrong, but after searching some more found out I WAS wrong. It would put the information into the restorehistory table if you used the LOADHISTORY option. which wasn't used in the question.http://msdn.microsoft.com/en-us/library/ms178615.aspx[/quote]Interesting. I missed that option when I read it the first time. It's sometimes handy to see restores in that table just to see who did what and when. But I wonder what use there would be for keeping a record of restore verifyonly executions? The only think I can think of is a senior DBA checking up on a jr. dba making sure they run restore verifyonly before running the real restore? But even that seems like a stretch.Wed, 21 Jan 2009 07:16:40 GMTJason Shadonixhttp://www.sqlservercentral.com/Forums/Topic640366-1461-1.aspxI got the question wrong, but after searching some more found out I WAS wrong. It would put the information into the restorehistory table if you used the LOADHISTORY option. which wasn't used in the question.http://msdn.microsoft.com/en-us/library/ms178615.aspxWed, 21 Jan 2009 07:11:12 GMTSteven Cameronhttp://www.sqlservercentral.com/Forums/Topic640366-1461-1.aspxI agree with Warren as well. I originally thought the answer was NO until I read the restorehistory docs which have a verifyonly entry, so I answered YES which came back as incorrect to my suprise.ms-help://MS.SQLCC.v10/MS.SQLSVR.v10.en/s10de_6tsql/html/9140ecc1-d912-4d76-ae70-e2a857da6d44.htmCould someone explain when the V = Verifyonly entry would be used for if there is NOT an entry made in this table with a RESTORE VERIFYONLY?Thanks!Wed, 21 Jan 2009 06:41:39 GMTdgabelehttp://www.sqlservercentral.com/Forums/Topic640366-1461-1.aspxI must be pretty bored today. I just tried it on both SQL 2005 and 2008, and niether wrote a record to the restorehistory table. One interesting thing I did observe... The backup file I used to play with was a backup of a database with several filegroups that live on different drives in production. On the dev box I was using that only has one, it actually spit out the same error message a regular restore does when you don't use the WITH MOVE clause to tell where you want those files to go. I found that slightly cool.Wed, 21 Jan 2009 06:40:08 GMTJason Shadonixhttp://www.sqlservercentral.com/Forums/Topic640366-1461-1.aspxThis answer is wrong. Just because SQL does not actually perform the backup, doesn't mean it won't store information about the RESTORE command. In that table, there's a restore_type that could be verifyonly: restore_type char(1) Type of restore operation:D = DatabaseF = FileG = FilegroupI = DifferentialL = LogV = VerifyonlyR = RevertCan be NULL.Wed, 21 Jan 2009 06:15:46 GMTLisa Philliphttp://www.sqlservercentral.com/Forums/Topic640366-1461-1.aspxI agree with Warren. I read the same BOL article and that's why I answered YES.By the way, the MSDN article quoted to justify NO being the correct answer doesn't even mention the msdb.dbo.restorehistory table.Wed, 21 Jan 2009 04:28:50 GMTJan Van der Eeckenhttp://www.sqlservercentral.com/Forums/Topic640366-1461-1.aspxSo why does the documentation for the restorehistory table show a setting of 'V' = Verifyonly for column restore_type?http://msdn.microsoft.com/en-us/library/ms187408.aspxWed, 21 Jan 2009 03:13:04 GMTWarren Gilberthttp://www.sqlservercentral.com/Forums/Topic640366-1461-1.aspxNot that obvious. ;)Wed, 21 Jan 2009 01:12:51 GMTChiragNShttp://www.sqlservercentral.com/Forums/Topic640366-1461-1.aspxObvious!Wed, 21 Jan 2009 00:52:44 GMTCarlo Romagnanohttp://www.sqlservercentral.com/Forums/Topic640366-1461-1.aspxComments posted to this topic are about the item [B]<A HREF="/questions/Restore/65450/">Restore of the Database</A>[/B]Tue, 20 Jan 2009 21:16:57 GMTfree_mascot