sql server - Why is a trailing SET inconsistently throwing an error in SQL? -


I'm seeing one of our web applications, and it was calling a stored procedure that was updated Was responsible for a record in the database.

There is no problem for the week in this stored procedure, and one day he started throwing errors, while debugging found us to be within the stored procedure.

It was originally a statement like this

  get started / do stuff set end  

then SET Never set anything up for some reasons it runs perfectly on our servers and until today, the client was running fine on the server until it decided to start the complaint. (Incorrect syntax error)

Is there any type of SQL server setting that can cause a sudden change in behavior?

Explanation - SET has always been in the process and running a SET by yourself, or the only statement in a stored procedure As it really works for me, this problem is, it should not work not so there is anything that is due to its working, when it should be unsuccessful?

A SET as usually fails to compile, even if Only SET can not be accessed:

  return process started as dbo.testproc1; The wrong syntax near the set 'SET' keyword  

Because the change fails, I can not see how the process can end up in the first place in your database?

Or maybe you were running in compatibility mode for SQL Server 2000 (which is still its permission.) Compatibility will break the process after changing mdoe to SQL Server 2005 or higher.


Comments

Popular posts from this blog

c# - How to capture HTTP packet with SharpPcap -

php - Multiple Select with Explode: only returns the word "Array" -

php - jQuery AJAX Post not working -