The forum will be down for maintenance over the weekend of August 18-20, 2017. The forum will be shut down on the evening (EDT) of Friday, August 18. Downtime is unknown but may be up to two days. The forum will be restarted as soon as maintenance is complete.

When I enter a syntax error on a query in Anywhere 12, I notice it takes around 45 seconds - 1 minute for it to come back and report the error. Is there anyway to fix this? I remember when we were using Anywhere 10 it would come back immediately.

I've noticed this behaviour on some of our client's servers during remote sessions. ISQL (Java) started from Sybase-Central executing an SQL statement with a simple typo (say SELET 1 FROM dummy) took some time (max. 15 sec) to come back with the error message.

The same statement issued with DBISQLC gets instantaneous response.

At that time I guessed ISQL (or the engine) might be looking for a translation for the error message or for user-defined error texts. Just to add some context: SC's language is usually set to DE. But I haven't seen that behaviour recently.

This bug was fixed in 12.0.1.3388 and later.
You can also get around the problem by installing the documentation (HTMLHelp).

FWIW: I guess here's the relecant CR description:

================(Build #3388 - Engineering Case #676033)================
When a statement cannot be executed by the Interactive SQL utility, the error is displayed in an error window. That window contains a "Help" button which, which clicked, can display a menu of relevant help topics (for the error message and for the type of statement being executed). Opening this error window could have taken a non-trivial amount of time if the online documentation for SQL Anywhere was not installed. In those cases, the software had to check with the DocComment Exchange (DCX) server to see if help was available for the statement in question. While the Interactive SQL utility is doing this check, it could be unresponsive. The problem was most acute on machines that were not connected to the internet at all. This has been fixed so that the error dialog opens without delay, and Interactive SQL remains responsive at all times.