SA17 EOL - Migrate to a different database provider - how?

[hansg]

Since SQL Anywhere is EOL at the end of 2025, we got an official email about that, we are looking how to continue our software in 2026 and further. The biggest issue in our situation is that we use a lot of Stored Procedures.

Some questions:

Does anybody already migrate SQL Anywhere with Stored Procedures to another database provider?

Do you know good migration tools? I did have a look at www.isperer.com, that looks ok. Anybody experiences whith that company?

What database provider(s) do you advice? PostgreSQL?

Tia Hans

[former_SQLA_member326303]

2025 or December 31, 2027? See the official SQL Anywhere information here

[VolkerBarth]

Just to add to the link posted by Illia:

AFAIK, the EOL date for v17 has been increased several times, possibly because no new majer version has been published...

In former times, a major version was usually supported until the second next version was released. That general rule won't work anymore, methinks.

@Mike Paola might tell more...

[MikePaola]

Hi all - the definitive source for EOMM dates is the SAP Product Availability Matrix (PAM). However, that requires an S-ID. For customers that don't have S-IDs, we decided to create that Wiki summary page - however, it should contain similar info - ie. they both indicate 12/31/2027 as the EOMM date for SQL Anywhere 17.

Now, I assume what prompted this thread is the recent communication that came out from SAP regarding the OEM program and options to extend to 12/31/2025. They outline various options available to OEMs beyond that date and also include an email address for questions - oempartner@sap.com. I would encourage anyone with questions/concerns to send their feedback to that email so that they are aware of your specific circumstances and can offer assistance.

Regards, Mike Paola

[hansg]

I sent an email to oempartner. I am very curious about there answer.