SQLA 12.0.1 Doesn't seem up to normal standards

[JimDiaz]

Is it my imagination or is 12.0.1 not up to normal SQL Anywhere standards? We have seen annoying issues such as passthrough syntax changes which force execution within a execute immediate, the requirement to lock all tables in a sql remote alter publication statement which place huge burdens on the remote administration of a database. Has SAP given up on SQL Remote replication believing Mobile Link is the answer?

Please let us know the road map for message based replication.

Thanks

Jim

[VolkerBarth]

passthrough syntax changes which force execution within a execute immediate

What exactly are you refering to?

FWIW, the problem with passthough statements sent against older remotes (that do not understand the new syntax) is not a new "feature" - for those cases execute immediate is the common work-around.

The "ALTER PUBLICATION needs exclusive access for all published tables"-feature is a new one (and not an improvement w.r.t. SQL Remote), so I agree with your statement on that part.

---

On the other hand, 12.0.1 has introduced HTTP/HTTPS as transport (rather lately, but after all), so I don't see that SQL Remote is EOL'ed feature-wise...

[JimDiaz]

WRT the passthrough syntax the issue is for example an insert statement which includes "on existing update" is changed in the passthrough statement to "on existing update defaults off" which fails when the passthrough is to an older database (9.0.2 for example).

I as the developer didn't include "defaults off" there was a reason I chose not to why in the world would the database change it. The syntax specified in help is

INSERT [ INTO ] [ owner.]table-name [ ( column-name, ... ) ] [ ON EXISTING { ERROR | SKIP | UPDATE [ DEFAULTS { ON | OFF } ]

This type of behavior leads me to believe that SQL Remote functionality was not considered in design or QA testing, which has never been the case in the past.