Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sp_DatabaseRestore @StopAt ignored when @ContinueLogs = 1 #1986

Closed
troyjennings opened this Issue Feb 27, 2019 · 2 comments

Comments

Projects
None yet
2 participants
@troyjennings
Copy link

troyjennings commented Feb 27, 2019

Version of the script
SET @Version = '7.3';
SET @VersionDate = '20190219';

What is the current behavior?
When @StopAt is not null and @ContinueLogs = 1, the StopAt value was not in the criteria for determining transaction log backups to apply.

What is the expected behavior?
When @StopAt is not null and @ContinueLogs = 1 only the transaction log backups up to the StopAt value would be applied.

zlthomps1 pushed a commit to zlthomps1/SQL-Server-First-Responder-Kit that referenced this issue Feb 27, 2019

zlthomps1 pushed a commit to zlthomps1/SQL-Server-First-Responder-Kit that referenced this issue Feb 27, 2019

BrentOzar added a commit that referenced this issue Feb 28, 2019

@BrentOzar

This comment has been minimized.

Copy link
Member

BrentOzar commented Feb 28, 2019

Great catch! Merged it into the dev branch, and I'll credit you for the March release. Thanks, and good work!

@BrentOzar BrentOzar closed this Feb 28, 2019

@BrentOzar BrentOzar added this to the 2019-03 milestone Feb 28, 2019

@troyjennings

This comment has been minimized.

Copy link
Author

troyjennings commented Feb 28, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.