#33 change "SQL Server vNext" references to 2019 #34
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
Working on #33. Didn't rename the vNext folder or edit the combined install scripts - wanted to keep the diff simple for my first PR here.
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.
Working on #33. Didn't rename the vNext folder or edit the combined install scripts - wanted to keep the diff simple for my first PR here.
Has been tested on (remove any that don't apply):
Known issue: the proc [cstore_doMaintenance] throws an error on my SQL Server 2019:
It was already doing that, though - I'll create a separate issue for that and see if I can fix it.