You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@gordthompson Thank you for the fix you provided! Your pr is fixing the issue you mentioned.
However, it caused a failure in our test lab which I had added the repro code as a test in this pr. Please have a look and test it. I will then go ahead and accept this pull request. Thanks again!
@v-afrafi Thanks for the follow-up. Your RegressionTest worked fine for me once I tweaked the DROP TABLE to run under SQL_2014. Using your test as an example I then added SelectIntoUpdateCountTest to verify the results of my original modification. Hope this helps.
This file contains hidden or 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
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.
fix for issue discussed on Stack Overflow here, where
SELECT ... INTOstatements always return an update count of -1