Comments
Sort by recent activity
After 4 hours of running Compare against different versions from our vault, to find where the "unexpected token" was coming from. I discovered one of our SQL developers had added a common table expression to a view. He did not realize that he added the table expression outside of the create statement. It was between the comments at the top and the actual create statement.
So syntax error that was not caught when he was testing the view was the culprit of the unexpected token. :lol: / comments
After 4 hours of running Compare against different versions from our vault, to find where the "unexpected token" was coming from. I discovered one of our SQL developers had added a common table exp...