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.
-
What is the compatibility level of the database project set to? (See second screenshot here simonlearningsqlserver.wordpress.com/2013/11/08/…)Martin Smith– Martin Smith2016-07-12 19:47:18 +00:00Commented Jul 12, 2016 at 19:47
-
Thanks. I never checked. It is SQL Server 2016 (130). I think it should be fine.user3616544– user36165442016-07-12 20:05:01 +00:00Commented Jul 12, 2016 at 20:05
-
Well if you're certain that you are using the most up to date version of SSDT report it here connect.microsoft.comMartin Smith– Martin Smith2016-07-12 20:17:48 +00:00Commented Jul 12, 2016 at 20:17
-
Upvote the following connect issue: connect.microsoft.com/SQLServer/feedback/details/2906200/…KorsG– KorsG2016-10-01 09:55:30 +00:00Commented Oct 1, 2016 at 9:55
Add a comment
|
1 Answer
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.
2 Comments
user3616544
Thanks. I will continue to use my own version of the string_split until Microsoft releases the fix.
rescdsk
Still doesn't recognize it in my installation!