Is Sybase ASE Dead?

A question the industry has been dancing around for years. We asked Vladislav Vlasov, Senior Developer at Ispirer, to stop dancing and give a straight answer.

Let's not waste time. Is Sybase ASE dead?

Vladislav: Clinically? No. Practically? It depends on who you ask and what year you think it is.

SAP announced the end of mainstream maintenance for ASE back in 2018. That deadline — December 31, 2025 — has now passed. So if you're running ASE 16.0 today, you are running a database that no longer receives new patches, no new security fixes, and no new features from the vendor.

But SAP did release ASE 16.1 with a maintenance date out to 2030.

Vladislav: They did, and that surprised a lot of people. ASE 16.1 came out in Q4 2022 with an end-of-mainstream-maintenance date of December 31, 2030. So SAP hasn't pulled the plug entirely.

But here is the important distinction people miss. Releasing a version and investing in a platform are two very different things. The engineering activity around ASE has been minimal for years. We are talking about incremental service packs, not innovation.

Meanwhile, SAP is pouring resources into HANA and its cloud strategy. SAP makes no secret of where its priorities are.

Where did this situation come from? Sybase used to be a serious player.

Vladislav: It absolutely was. Sybase was founded in 1984 in Berkeley, California. They shipped the first version — originally called Sybase SQL Server — in 1987 for UNIX-like platforms. At a time when Oracle owned the market, Sybase had something genuinely different: a true client-server architecture that was faster for online transaction processing.

And then Microsoft got involved.

Vladislav: Exactly. In 1988, Sybase, Microsoft, and Ashton-Tate co-developed a version for OS/2. Microsoft sold it as Microsoft SQL Server. For several years, the two products were essentially identical — until 1993, when their co-development agreement expired, and they parted ways.

Microsoft bought a copy of the source code and went in its own direction for Windows. Sybase continued on UNIX-like platforms. In 1996, Sybase renamed its product to Adaptive Server Enterprise — ASE — specifically to avoid confusion with Microsoft SQL Server. And the irony is that both products still share T-SQL, the same query dialect, because they came from the same original codebase.

So Sybase survived the Microsoft split. Then what went wrong?

Vladislav: The acquisition. SAP bought Sybase in July 2010 for $5.8 billion. On paper, it looked like validation — a massive premium, a Fortune 500 acquirer. But if you read the SAP press release carefully, they were not buying ASE. They were buying the mobile platform. Sybase iAnywhere. The financial sector relationships. The analytics product, which became SAP IQ. ASE was essentially a passenger on that deal.

SAP spent six months just figuring out how to run SAP ERP on Sybase. The focus was never on making ASE more competitive as a standalone product. And by 2014, SAP had stopped using the Sybase brand entirely.

What happened to the customer base?

Vladislav: The financial sector held on the longest. Banks, trading platforms, and clearing systems — these were Sybase's stronghold for decades. High-concurrency, mission-critical workloads running on UNIX-like systems. ASE delivered years of uptime on these systems, and there was no urgency to touch what was working.

But after the 2018 EoMM announcement, the math changed. Some estimates suggest that roughly 50% of users had already left within the first three years of that announcement. When your vendor is steering investment elsewhere, and your security patches have an expiry date, the business case for staying erodes fast.

You mentioned security patches. How serious is that concern in practice?

Vladislav: In finance, for example, it is existential. The average cost of a data breach is already in the millions — some estimates put it above $6 million per incident. A database without active security maintenance is a compliance problem. Regulators and auditors expect you to be running fully supported software. When you can no longer point to a vendor support contract, you are in a grey zone that nobody in a regulated industry wants to be in.

Is there any scenario where staying on ASE makes sense today?

Vladislav: There are a few. If you have very stable, air-gapped workloads with no external attack surface, the security argument weakens slightly. There are also third-party support providers who fill the gap — they offer security backports and SLAs for ASE, typically at 50 to 70 percent lower cost than SAP's own maintenance. That buys time.

But "buying time" is the key phrase. It is not a strategy. It is a pause.

So where are people migrating to?

Vladislav: PostgreSQL is the primary target, same as we see from Oracle migrations. It handles the transactional workload, it is open-source, and the community support is enormous. The ASE-to-PostgreSQL path also has a technical advantage that people overlook: because ASE and Microsoft SQL Server share T-SQL heritage, a lot of the stored procedure logic is not as foreign as it would be coming from, say, Oracle PL/SQL. There is still work to do, but the dialect gap is smaller.

For analytics, we route to ClickHouse or similar column-oriented systems. The principle is the same as any legacy migration: separate your OLTP from your OLAP, and stop trying to make one system do everything.

Any final verdict?

Vladislav: Sybase ASE is not dead in the sense that it still runs. There are production systems on it right now, tonight, processing real transactions. The engineering inside it — the row-level locking, the replication server, the *NIX-native performance — was genuinely excellent for its era.

But it is a database on life support from a vendor that has moved on. The question is no longer if you migrate, it is how carefully you plan the exit. Every quarter you wait, the pool of engineers who know ASE shrinks, the security exposure grows, and the cost of the eventual migration increases.

The best time to start was 2018 when the announcement was made. The second best time is now.