My company is planning to upgrade from SQL Anywhere 10 to 17, and I recently did a test where I rebuilt the consolidated database in version 17, and attempted to see if it could continue replicating against version 10 remotes. Not only did it refuse to accept message files from the version 10 remotes in dbremote (it stated there was a missing message for all the remotes that sent), the consolidated was unable to send, complaining that a transaction log was missing. I translated and examined all of the transaction logs, and everything looked at it should, nothing appeared to be missing.
Am I missing something about how to upgrade a replicating database between versions? I recently did a full rebuild of the same consolidated database in version 10 (to shrink it) and it had no problem replicating after.
asked 06 Jun '16, 10:58
Warning! Thread Drift!
Based on anecdotal evidence from the field, SQL Anywhere 16 is a solid and reliable version for conservative enterprise database installations. This includes large MobiLink and SQL Remote installations.
In fact, it is entirely possible V16 may earn a spot in the SQL Anywhere Best Versions Ever Hall Of Fame (SABVEHOF) alongside 5.5 and 9, even though "16" is an even number :)
Personally speaking: The next version of Foxhound will support target databases running on SQL Anywhere 17 but Foxhound's own embedded database will continue to ship as V16 (it will also run on V17, but it has not been upgraded).
Question for SAP: Are you dogfooding V17?
I.e., for those existing SAP products that run earlier versions of SQL Anywhere (not just 16 but earlier), have you upgraded and shipped them using V17?
Here's an thought-provoking discussion of dogfooding (and beta testing, for that matter): How Proper "Dogfooding" Might Have Saved Facebook Home.
...and for the tldr crowd, here's the graphic novel version :)...
answered 07 Jun '16, 06:26