5

Try to use SQL Server 2016 STRING_SPLIT function in a stored procedure. It parses correct in SSMS. But in SSDT (latest version), the function can't be resolved, so the project cannot be compiled. Anybody know how to solve this? Thanks.

4

1 Answer 1

2

This is a known bug in SSDT and we have a work item internally to fix it. The only workaround I can suggest, unfortunately, is to remove the STRING_SPLIT from the stored procedure definition and then alter the definition of the stored procedure as a post-deploy script action.

Sign up to request clarification or add additional context in comments.

2 Comments

Thanks. I will continue to use my own version of the string_split until Microsoft releases the fix.
Still doesn't recognize it in my installation!

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.