We are getting the below message sometimes while executing the stored procedure, after that without any change deleting and re-executing the stored procedure it is working fine.
If anyone hits this error after having deployed via a Visual Studio database project then it's worth checking the properties of your stored procedure file. If this is set to Project Default then go to the properties of your database project > Project Settings and click the Database Setting button.
You can turn these two values (and others) to be on by default as shown in the screenshot below.
This will only fix the issue if you have changes to the procedure how ever; a schema compare and subsequent update will not change the QUOTED_IDENTIFIER
in the stored procedure unless there are changes to the body of the procedure. It will prevent the problem from reoccurring on a subsequent schema updated though.