Start-DbccCheck, better extraction of errors #9624
Open
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.
Type of Change
Invoke-ManualPester
)Purpose
Test-DbaLastBackup reported "" instead of the errormessage of checkdb. Checking Start-DbccCheck I noticed that the error wasn't parsed correctly in all cases... this strategy aims to preserve the most of the error message without splitting "blindfully" as before. Notice that probably different PS versions and MS libraries can change the result, so this probably slipped in some time ago and went unnoticed.
Approach
Extract in a loop the innerexception. Split only if text is actually found on the string
@johnsterrett thanks for the report