One Database Blocking Full Cloud Adoption
The firm's broader infrastructure roadmap called for consolidating on Azure, but its trading support and reporting database remained on an on-premises Sybase ASE instance with no cloud-native path forward.
A financial services firm needed to exit an on-premises Sybase ASE environment for a cloud-scalable, Entra ID-integrated platform. S2SIM handled the ASE-to-SQL Server dialect mapping while OptiSol validated cutover against the firm's Always On Availability Group requirements.
The firm's broader infrastructure roadmap called for consolidating on Azure, but its trading support and reporting database remained on an on-premises Sybase ASE instance with no cloud-native path forward.
Access to the ASE environment relied on a separate credential system disconnected from the firm's Entra ID-based identity governance — a standing exception in an otherwise centralized access model.
High availability for the ASE instance depended on Replication Server configurations that were expensive to maintain and increasingly difficult to validate against the firm's current resilience standards.
Because Azure SQL Managed Instance's high-availability model works fundamentally differently from ASE Replication Server, OptiSol treated Always On Availability Group validation as a first-class cutover gate, not a post-migration afterthought.
S2SIM catalogued the trading support schema, stored procedures, and T-SQL dialect patterns, scoping the conversion against Azure SQL Managed Instance and flagging every feature with no direct managed-instance equivalent.
Schema and stored procedure signatures were converted automatically from ASE T-SQL to SQL Server T-SQL, with the bulk of syntax and datatype differences resolved without manual rewriting.
Engineers resolved cursor and error-handling differences that required contextual judgment, then ran a full regression suite against the reporting and trading support workflows.
Before cutover, failover behavior was validated against the firm's Always On Availability Group resilience standards, and Entra ID integration was confirmed for the new environment's identity and access model.
"We didn't just move the database to Azure. We proved its failover behavior met our resilience standard before we trusted it with trading support." — OptiSol S2SIM Delivery Lead
Let's Talk
Tell us what you are running today and where you need expert support.
"*" indicates required fields
Global Presence
Five global locations. One connected engineering team.
North America
Chennai · Coimbatore
Client services
Regional operations
Client services