Skip to Main Content
Cloud Platform


This is an IBM Automation portal for Cloud Platform products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Status Under review
Workspace DevOps Automation
Categories Deploy
Created by Guest
Created on Apr 18, 2025

Database Migration Tool

As we move to a cloud deployment to EKS we want to move our On-Prem DB into the cloud as well.  This will help to ensure the best performance that we can get.  As part of this effort, we want to switch database technologies for cost savings.   We began to investigate the migrate-database.sh but were told that the tool would not suit our needs.   

In our case, we have a very large SQL Server database (over 6TB) and will have only one shot to properly migrate the database.  After discussions with our DBAs we are very concerned about trying to take on this effort ourselves as we do not know the underlying architecture of the database.   This could lead to many unpredictable errors, for example, incompatible data types that could result in lost or altered data.  The errors that arise from this type of issue can take weeks to months or even longer to identify, at which point it could be too late to recover and could be very difficult to develop tests to verify.

We are requesting a tool that would let customers migrate between any of the supported database architectures.  Perhaps there could be an intermediate step that you  convert from DB1 to "something" and then from "something" to another architecture.   This would solve the issue of having many iterations of one DB to each of the others.

Ideally, the tool would be re-runnable, only migrating new data each time.   When migrating a very large database, it could take a very long time (days?) which is an issue for at least two reasons.

  1. If the migration is interrupted for any reason (network drop, error, etc.) starting over could be problematic with schedules.
  2.  In order to avoid extended downtime, it would be helpful to move the data while users are still using the old database.  Once the migration catches up, it can be run as needed to keep the new and old databases in sync until to actual move date.  This avoids bringing the tool down during the migration.

While this tool may not be used frequently, it would be an important tool that could aid customers trying to move to the cloud and/or looking for other cost savings.

  • Admin
    Randy Langehennig
    Reply
    |
    Apr 22, 2025

    Thank you for submitting this idea. We are going to create a discussion topic and will review this idea with our development team soon. We will be in touch with updates.