Raincode IMSql:
Technical Discussion


Raincode IMSql is a solution for migrating mainframe IMS applications to Azure SQL. Together with Microsoft we’ll discuss how Azure SQL is optimized to handle high volume transactional workloads that are currently hosted on mainframes.

The Discussion

Microsoft has been investing heavily in helping customers migrate their critical Tier 1 Mainframe workloads to Azure. While Raincode’s cloud-native strategy fits perfectly in this strategy, IMS is a very specific kind of workload. How does IMS workload modernization differ from typical COBOL/DB2/CICS modernization efforts? 

The Speakers

Ulrich Homann

MicrosoftCorporate Vice President

Microsoft Corporate Vice President and Distinguished Architect in Cloud and AI technologies with 30+ years global experience in development, design and large-scale deployment of software systems and solutions, Ulrich (Uli) is a versatile solutions architect with a wide range of hands-on know-how about architecture and assembly of solutions from originating components to complete products and operational solutions. 

Markus Lindström 

RaincodeChief Technical Officer

Chief Technology Officer of Raincode, Markus worked extensively on the integration of the Raincode product line with Azure. With over 15 years of experience in the industry, he is a seasoned professional with extensive knowledge and expertise in networks, databases, compilers and programming languages. Prior to Raincode, Markus worked in the banking sector and had been teaching for years at the Université Libre de Bruxelles. 

Asad Khan

MicrosoftVice-President and General Manager for SQL products and services

As the Vice President of SQL Products and Services, Asad leads engineering and product management for SQL Server and all Azure SQL Services, including Data Migration Services and Microsoft investment in Hybrid, such as Arc Data Services.  


Watch it NOW!

Raincode IMSql is a unique solution to migrate IMS workloads: it does not transform the code or the data.

Deciding for or against transforming programs and/or data as part of the migration project may seem like a secondary issue, but it is not. It makes or breaks migration projects.
At the code level, being non-transformational means that the core value of the application, namely, its business logic, is preserved, and does not go through a potentially disruptive process that will change its structure, just for the sake of an infrastructure change. It also means that the application can keep on being maintained during the migration project.
And on the data side, it is even more impactful. If the data must be analyzed, normalized, converted for the project, its migration becomes a project in its own right.