Deprecation of Support for SAP ASE Versions

We want to inform you about an important update regarding the SailPoint SAP Sybase connector. Currently, our connector supports SAP ASE 16.0 SP03, ASE 16.0, and Sybase ASE 15.7. https://community.sailpoint.com/t5/Connector-Directory/Sybase-Connector/ta-p/153174

As you may know, SAP has announced that mainstream maintenance for SAP ASE 16.0 will end on December 31, 2025. After this date, no new patches or enhancements will be provided by SAP. While paid support may still be available, certain features—including the 32-bit Backup Server, TLI, and OpenSSL in specific Service Packs—have already been deprecated.

This shift encourages users to transition to newer versions, such as 16.0 SP03 or SAP ASE 17, which offer modern features and enhanced security.

In line with SailPoint’s support policy and our commitment to providing the best possible service to our customers, we must align our support with SAP’s APIs and product recommendations. Therefore, we will be deprecating support for SAP ASE 15.7 and 16.0, effective December 31, 2025. While the integration will continue to function as-is for these deprecated versions, please note that there will be no new features or bug fixes. Out-of-the-box support for these versions will conclude on December 31, 2026.

We remain committed to supporting SAP ASE 16.0 SP03 and will continue to integrate with new versions of ASE as part of our ongoing roadmap.

Key Details:

  • EOMM for ASE 16.0: December 31, 2027.

  • EOMM for ASE 16.1: December 31, 2030 (planned for release Q4 2024/Q1 2025).

  • What EOMM Means: SAP stops delivering new corrections, technology updates, legal changes, or patches; you only get customer-specific problem resolution, often at extra cost.

Implications for Users:

  • Security Risk: Running unsupported software leaves systems vulnerable to security flaws.

  • Compliance Issues: May breach contracts or regulatory requirements.

  • Planning Needed: Organizations must decide whether to move to SAP ASE 16.1, explore third-party support, or migrate to cloud databases.

Action Required:

  • Confirm Your Version: Identify your specific SAP ASE version (16.0 or 16.1).

  • Assess Your Strategy: Decide on your long-term support plan before the 2027 deadline.

Thank you for your understanding and continued partnership.

Hi @vivek_shrivastava

Thanks for sharing this update, really helpful for planning ahead. :folded_hands:

A couple quick clarifications that would help teams line up their upgrade plans:
1.After Dec 31, 2025, which ASE versions will be officially supported? (I noticed the post mentions 16.0 SP03, and the connector docs also mention 16.0 SP04 — just want to make sure we’re targeting the right one.)
2.When you say “deprecated effective Dec 31, 2025”, should we interpret that as: no new fixes/enhancements going forward, but existing integrations should continue to run — and Support would be available through Dec 31, 2026?
3.Does this apply to IdentityIQ only, or also ISC?
4.Do you have a recommended “safe target” version for customers upgrading from 15.7 / older 16.0 (and any common upgrade gotchas to watch for)?

If you have or plan to publish a short upgrade checklist / compatibility matrix, that would be amazing and would help a lot to avoid surprises.

Hi @amrdodani please find my answers below

  1. After Dec 31, 2025, SAP SSE 16 SP03 will be supported OOTB
  2. “Deprecated effective Dec 31, 2025”, implies that: no new fixes/enhancements shall be done wrt deprecated versions going forward, but existing integrations should continue to run — and Support would be available through Dec 31, 2026. If bug fixes or enhancements are required, custoemrs will need to update to new SAP ASE version 16 SP03
  3. We have the same connector working for IIQ as well as ISC, so this applies to both.
  4. The recommended “safe target” version for customers upgrading from 15.7 / older 16.0 is SAP ASE 16 SP03