Comments
5 comments
-
Its possible there is a problem in the parser, did you send in an error report? Can you share some snapshots?
-
I just encountered this issue again. This time I sent a report, and referenced the title of this thread in the body of the problem description.
-
Hi @JohnES,
Just updating the forum post here with the progress from the ticket. This issue appears to happen when you have the following:
1.SET ANSI_NULLS ON
at the end of a proc (with no preceding GO statement)
2. "Ignore SET QUOTED_IDENTIFIER and SET ANSI_NULLS statements" and "Add WITH ENCRYPTION" are both enabled
3. "Ignore WITH ENCRYPTION" disabled
We are looking into this from our side.
Thanks again for your help, John! -
You're Welcome Jessica.
Thank You for your help sorting this out. -
Hi @JohnES !
This issue is now resolved in the latest frequent release update, SQL Compare 13.6.8.8602. You can get this from Help>Check for updates (you need to make sure Help>Configure frequent updates is turned on).
Add comment
Please sign in to leave a comment.
I just did an update yesterday, to 13.6.7.8464. Before that everything worked fine, and I've never come across this error before.