Fix backup dbadatabase dateconversion #5753
Merged
Conversation
This file contains 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
The '-' character was failing to implicitly convert in T-SQL from string to datetime - due to certain locales. Explicit conversion should resolve using known format 120.
This was referenced Jun 17, 2019
4 tasks
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.
Type of Change
Purpose
To fix locale issues in datetime conversions under Get-DbaBackupHistory - due to '-' character certain locales couldn't handle the implicit conversion
Approach
Change to explicit conversion using CONVERT and format 120 (yyyy-MM-dd hh:mi:ss)
Commands to test
Get-DbaBackupHistory with -Since specified