I noticed SAP has not released an EBF for SQL Anywhere 17 (Windows on X64 64BIT) in over 5 months, the longest gap in-between EBF's in at least 6 years. A month ago, I submitted a support ticket/question on SAP For Me about when we could anticipate a new update and was told that one would be coming soon, and that SAP was currently testing. One month later, nothing. Anyone know anything? Should I not be concerned about the lack of a recent EBF?
The end of SQL Anywhere? This is news to me. As product owner I feel like I would probably know. The EOM, the absolute minimum maintenance date for SQL Anywhere has been pushed out to Dec. 31, 2028. This means that 17.0 SP1 will be supported by engineering at the very least until that date. The date doesn't get pushed out too far into the future because if a new version comes out we don't want to be held responsible to support two versions at the same time for too long.
The reason that this latest EBF has taken so long is that we've upgraded the compiler, gone through extensive testing and had to deal with a number of issues as a result. The windows patch is on the verge of being released as all testing has completed.
I'm not sure where you saw that but it doesn't even make sense to have an EOL date before an EOM date. Perhaps you are referring to some SQLA OEM agreements being discontinued at the end of 2025. That statement had no implications on the SQLA EOM date and says nothing about a SQL Anywhere EOL date which has never been announced.
As product owner I feel like I would probably know.
Jason, IMHO it would be helpful if SQL Anywhere product owner(s) and marketing people would post within this forum more frequently - several questions on the "SQL Anywhere Future" had been asked in the last year and were discussed by customers for weeks or months before an "official SAP answer" was posted (say, by Mike Paola).
Those were basically OEM-related questions, but it easily leaves the impression that all things SQL Anywhere-wise are about to going down slowly... - in that respect I share André's impression.
Jason, it would be good to also share this concept inside SAP, because a lot of SAP sales representatives refer to the current EOM date as being really the end date for SQLA. So talking to them you always get the impression that after 2028 we wont have any SQLA anymore.
This is Michael Fischer. We have been the largest distributor of OEM licenses in Germany for almost decades, and as of today, we seem to be the last. There is significant uncertainty among our customers regarding the future of SQL Anywhere, and we would very much like to get in touch with you as the Product Manager to discuss this further. We would appreciate it if you could contact us via email at mifi@appfact.de.
Thanks Chris! Question for you. Is there a reason why the associated KBA isn't updated the same day the new EBF is posted for download so that notifications would be sent to SAP For Me users that have that article "favorited"?
Chris and Reg - noticing another 4+ months has passed since Build 7672. While this may be a bad assumption on my part, maybe the delay is due to the focus on the migration of the forum or other tasks? Regardless, any rough idea when we can expect a new update?
There will be an new EBF (17.0.11.7801) in ~7 weeks. This is what SAP told us: "we had to wait for some other fixes to go into the next SP for SQL Anywhere. We will make a new build this week and then QA will start doing tests. If we do not find show-stoppers then an new SP will be available in about 8 week. The time can be shorter, but we cannot be more accurate."
You did read about the end of sql anywhere, correct?
So this is how products are dying today, less and less investments in the qualtity of the product.
Should you be concerned, perhaps, but you must anyway have a plan on where to go with your database in the next 18 months.
We are currently sheduling the move from sql anywhere 17 to postgresql, and we are wondering what this will result performance wise, as we have many large tables in frequent use.
André, where did you read about the "end of SQL Anywhere"? Currently the EOL for SQL Anywhere is December 2027 (and it has been enhanced at least twice in the past), and according to SAP Product Availability Maxtrix, is even December 2028, see Chris Keating comment here...
(If you are relating to the OEM edition, that's another issue, but that seems to be in discussion, see that thread, too.)
Thank you Volker for that clarification. We're not using the "OEM edition" and I do see now the SAP PAM does indeed say 12/31/2028 for SQL Anywhere 17.
With that aside, do you feel it's odd that's it's been this long without an EBF for Windows X64? I'm probably overthinking this, and it's probably stemming from us finally trying our best to stay on top of applying the latest EBF releases for security purposes.
applying the latest EBF releases for security purposes
In my understanding, SQL Anywhere EBFs are usually more about "functional bug fixes" and/or adaptions to changes in third-party software and less about security fixes. The whole version 17 readme file, which lists fixes since its introduction in 2015, contains only a few security topics so I do not expect that EBFs have to be published frequently to deal with that. Just my 2 cents. 🙂
Yes, I agree, definitely more functional bug fixes. But, if there were a security issue to address, it would be in there I would assume. For example, an update to the embedded JVM.
The delay in the EBF release for SQL Anywhere 17.0 SP1 PL15 Build 7672, which is now available for Windows and Linux, was because of a change in compilers, which lead to a lengthy testing process.
If there was a security issue that had required us to publish a fix during this time, we have a a process where we go back to the source code for the last released EBF, apply the fix for the security issue (it's often a 3rd party component), and then rebuild and retest the software. Since there is very little that has changed, the testing of that change is typically straightforward. If you look back on the SQL Anywhere releases, you can spot a "security" release as it is typically one build higher than the previous release. You'll see that we released builds 7058 and 7059 for Linux and Windows, and build 7059 was a security release.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.