Navigating the Transition from SQL Server/Oracle to Db2: A Perspective for Maximo Users

Navigating the Transition from SQL Server/Oracle to Db2: A Perspective for Maximo Users:

As IBM prepares to end support for Maximo 76 in September 2025, organizations using Maximo are facing a significant decision: transitioning to the Maximo Application Suite (MAS) 9 and how to optimize the resources available to use Maximo Application Suite significantly. Many organizations are looking to setup MAS instance in their data centre while many of them are planning to utilize cloud and migrating their Maximo 76 to MAS on Cloud. One of the important decision to take while setting up MAS is to decide on database that will be used.

Understanding the Database Landscape – Why DB2 Migration?

Maximo 76 and Maximo Application Suite (MAS) 9 both supports Db2, Oracle, and SQL Server. But if you are planning to upgrade to Maximo Application Suite, It might be important to consider the database you choose. Here’s why:

1. Db2 Comes with MAS Licensing: For organizations opting for MAS, Db2 is bundled with the license, making it a cost-effective choice. This is particularly appealing in contrast to Oracle and SQL Server, which require additional licensing fees. Given the footprint of MAS, this adds up to a significant cost.
2. SaaS Migration Requirements: If moving to IBM’s Software as a Service (SaaS) offering, Db2 is database of choice and your database need to be migrated to Db2.

The Complexity of Migration:

Migrating from SQL Server or Oracle to Db2 is not a simple task. This process involves several complexities that organizations need to carefully consider:

1. Data Migration Challenges:

• Schema Differences: Db2 , Oracle and SQL Server have different data types, indexing strategies, and system functions. These discrepancies necessitate a comprehensive schema mapping and conversion process.
• Data Integrity: Ensuring that all data is accurately transferred without loss or corruption is crucial. This involves extensive testing and validation.
• No Readymade Tool: There is no readymade tool available in market which can do end to end conversion from SQL Server/Oracle to Db2 while ensuring and maintaining the complex data integrity requirements of Maximo. Sedin has developed set of tools which can be used to smoothly migrate data from SQL Server or Oracle to Db2.

2. Application Compatibility:

• SQL Dialects: Db2, Oracle and SQL Server use different SQL dialects. Application queries written for Oracle or SQL Server need to be rewritten or adjusted to be compatible with Db2.
• Business Logic Adjustments: Custom applications and business logic built around SQL Server or Oracle may need significant modification to work with Db2 capabilities and constraints.

3. Performance Considerations:

• Tuning and Optimization: SQL Server, Oracle and Db2 have different performance tuning mechanisms. After migration, performance optimization is required to ensure that the application runs efficiently on Db2.
• Query Optimization: Queries optimized for SQL Server or Oracle might not perform well on Db2, necessitating query performance tuning.

Strategic Considerations for a Smooth Transition:

1. Thorough Planning: Develop a detailed migration plan that includes a timeline, resource allocation, and risk management strategies. Consider engaging with experienced consultants to guide the process.
2. Seamless Execution: Acquire tool, knowledge and expertise for migrating SQL Server or Oracle to Db2 also the deep knowledge of data integrity of Maximo Objects.
3. Testing and Validation: Conduct rigorous testing to ensure data integrity, application functionality, and performance benchmarks are met before going live.
4. Training and Support: Invest in training for your system admin team to ensure they are proficient with Db2. Additionally, establish a support plan to address any post-migration issues

Conclusion:

Migrating from SQL Server or Oracle to Db2 is a complex process that demands careful planning and substantial resources. If you're navigating this transition and need assistance with planning or executing the conversion, consider reaching out to the expert team at Sedin. Our team has developed a suite of tools specifically designed for successful database conversions from SQL Server or Oracle to Db2. Let us help streamline your migration process and ensure a smooth transition to Db2.

Author: 

Prashant Sharma

Delivery Head - Maximo & EAM360