How can we help you today? How can we help you today?

SQL Compare shows syntax error while SQL Server accepts syntax (SCHEMABINDING)

I'm able to run the following script against a 2017 version of SQL Server.
GO
SQL Source Control doesn't save the SCHEMABINDING = ON for the security policy, and when I tried to add it manually to source control and then compare against local, it says that it's a syntax error and ignores it. However, SQL accepts it and the option is valid according to microsoft docs. (https://docs.microsoft.com/en-us/sql/t-sql/statements/create-security-policy-transact-sql?view=sql-server-2017)

Am I doing something wrong or is this a bug that needs to be fixed?
James
0

Comments

2 comments

Sort by
  • Alex B
    Hi JamesW ,

    I've deleted the duplicate of this post so you may have received a message indicating that.

    For the question here, I see the same occurring and have raise the issue with the development team as SC-10673.  I will update here when I have more information from the team!

    Kind regards,
    Alex
    Alex B
    0
  • JamesW
    Thanks! I'll work around it for now. (Not sure if I was supposed to accept the answer or not :smile:)
    JamesW
    0

Add comment

Please sign in to leave a comment.