Get-DbaDbRestoreHistory - additional restore point info request #7854 #7855
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.
Included BackupStartDate along with StopAt & a combination of the two to provide the LastRestorePoint - being either the stopat point or the start of the last restored backup
Type of Change
.\tests\manual.pester.ps1
)Purpose
Adds additional information to the output of the function relating to the point in time of the restore.
Approach
Additional fields returned in SQL statement
Commands to test
Same as before just provide additional lines of output
Screenshots
Shows the new output and the LastRestorePoint being the start of the differential backup.
This shows the output of the SQL queries used in the script. Demonstrating the LastRestorePoint returned as the stop_at point:
The following shows the output with the last file being a transaction log created after the stop at point but covering the required time. The LastRestoredPoint is shown as the stop at point not the .trn file datetime (UTC, rather than BST)
Finally the log backup not being after the stop at time therefore the stop at time can't be used and the point in time will be that of the backup file.