(FM-3706)Create database with optional compatibility breaks CI #152
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
cowofevil
pushed a commit
that referenced
this pull request
Sep 24, 2015
…tional_compatibility_breaks (FM-3706)Create database with optional compatibility breaks CI
cowofevil
deleted the
FM-3706/Create_database_with_optional_compatibility_breaks
branch
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.
Before this PR, the test case was creating a database with compatibility_level is 120 which only applies to SQL Server 2014 to SQL Server 2016, so the test case failed when being tested against SQL Server 2012.
This PR changes the compatibility level to 100, this level applies to SQL Server 2008 to SQL Server 2016