In Visual Studio 2013, I have created a database project and imported an existing database. At first all was fine, and the project built and produced create scripts.
However, now Visual Studio seems to think that there are SQL syntax errors, returning several SQL46010: Incorrect syntax near:
errors. These are all from code generated by VS - I have not written any of it.
Example 1:
ALTER ROLE [db_owner] ADD MEMBER [SomeUser];
SQL46010: Incorrect syntax near ADD.
Example 2:
DECLARE @Foo NVARCHAR(7) = 'abcdefg';
SQL46010: Incorrect syntax near =.
If I copy/paste the code into SSMS, everything works fine.
Unfortunately, these prevent the project from building, which means I can't publish. Since they are errors, not warnings, I cannot set them to be ignored in the project settings.
A workaround exists where I can set the problem files' Build Action to None, but I need these files included when I publish.
I have tried:
The closest problem I have been able to find is this MSDN thread from 2012, stating that there is a bug SSDT SQL parser (which prompted me to try updating SSDT).
There is a setting in the project properties called Target platform
that tells VS what version of SQL Server to check the syntax against.
These are relatively new additions to the T-SQL syntax, and they might not work if the syntax was set to e.g. SQL Server 2005.