Remove invalid "NOUNLOAD" option from docs example#4197
Merged
ktoliver merged 1 commit intoMicrosoftDocs:livefrom Apr 28, 2020
Merged
Remove invalid "NOUNLOAD" option from docs example#4197ktoliver merged 1 commit intoMicrosoftDocs:livefrom
ktoliver merged 1 commit intoMicrosoftDocs:livefrom
Conversation
The NOUNLOAD option is for restoring from tape, and this example is restoring from a disk source.
Contributor
|
@jadarnel27 : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
Contributor
|
Thank you, @jadarnel27 - verifying |
kfarlee
approved these changes
Apr 27, 2020
Contributor
|
#sign-off |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The NOUNLOAD option is for restoring from tape, and this example is restoring from a disk source.
I found the example code a little confusing because of that option. It's not clear why it's there, and according to the docs the option is simply ignored in this case.
Referencing this MS Docs article:
RESTORE Statements - Arguments (Transact-SQL)
Which states: