Task/rdmp 137 MDF attacher override #1729
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
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.
Situation:
A SQL .MDF file is copied from a linux server to a windows machine hosting RDMP at a regular interval.
The .mdf file name changes each time.
Currently, each time an MDF data load is run, the override for the linux filepath -> windows filepath needs to be updated (/var/opt/mssql/data/mydb.mdf -> C:\Users\me\mydb.mdf)
Improvement:
Allow for the directory to be specified without the file name, this will allow for the recurring data load to be ran without modification ( assuming the .MDF and .LDF files are copied to the same directory each load)
Solution:
When specifying the MDF and LDF override locations, if a directory is set it will automatically attempt to update the attacher to use the local filesystem location rather than the original file system location.
Steps to test: