-
Notifications
You must be signed in to change notification settings - Fork 1k
Description
Version of the script
SELECT @Version = '8.25', @VersionDate = '20250704';
What is the current behavior?
This is more of a documentation issue, I think. I wanted to use sp_DatabaseRestore to recover the latest (last night's) full backup from a NAS share to a reporting instance. But not all the logs since that backup. Just the full please. @ContinueLogs=0 doesn't do this (that's also not clear from the documentation). However, omitting the @BackupPathLog parameter does have this useful side-effect. But that's not documented in the existing docs, either here on on Brent's page on this proc.
If the current behavior is a bug, please provide the steps to reproduce.
Run the proc with @database, @BackupPathFull specified with test backup data, add @ContinueLogs = 0 + @RunRecovery = 1, and observe the difference in behaviour when @BackupPathLog is added and removed (or explicitly set to NULL)
What is the expected behavior?
I don't know. I presume this is intended behaviour (good for my use case, anyway), but AFAICS no documentation of it anywhere.
Which versions of SQL Server and which OS are affected by this issue? Did this work in previous versions of our procedures?
N/A