Support for Db2 Web Query was pulled a few years ago, and many companies migrated away immediately. But, at COMMON PowerUP26 this spring, we were surprised by a couple of things:
First, we were surprised at the amount of people who said they were still running Web Query. They’re running without support until they’re forced to migrate.
Second, was the amount of people who tried to migrate and found it harder than they expected. There is a reason some migrations stall, and it’s worth understanding before you look for a Db2 Web Query replacement.
The big reason: Nothing is a true one-to-one swap for Web Query.
Whatever tool you pick, it will not reproduce your reports on its own. You’ll likely need to re-create those reports, and sooner or later you will hit something that the new tool does not handle out of the box.
The most important thing in a Db2 Web Query replacement
Imagine you’re going through a Web Query migration, and you realize that the new tool doesn’t quite do what you needed. Or, it’s missing a small feature you thought it had. You’re already invested in the tool. You don’t want to start over. What do you do?
It all comes down to the vendor behind the software. The most important thing to look for in a Db2 Web Query replacement is not a feature. It’s a vendor who will make sure you don’t get stuck.
That’s not to say that the features don’t matter. Of course they do, and you should still ensure that any tool you choose can do everything you need. But, once you have that, the real difference maker is how much the vendor will work with you if/when you need help or hit a roadblock.
When you realize the software is missing a feature you need, most vendors answer with “the software can’t do that” or “it’s on the roadmap.” Then, you’re tasked with finding a workaround.
The vendor you want for a project like this is one whose team will work with you to meet your needs, and even goes so far as to update the actual product when needed.
Real Web Query migration example: A 3-person team replaced 300 reports in-house
Here’s an example of one company who went through the migration process. Cat Pumps ran on Db2 Web Query for years before having to replace it. They used m-Power (mrc’s low-code development platform), and rebuilt the whole reporting environment in-house. A three-person team converted more than 300 reports without bringing in outside services.
One key factor in the success of this project was the support behind the tool. When Cat Pumps hit something they could not figure out, mrc’s support team walked them through it. In the cases where the tool did not do what Cat Pumps needed, the request went to mrc’s developers and the product was changed to fit.
“If you run into any type of issues, they’re right there to hold your hand and get you through it,” said Steve Keller, IT Director at Cat Pumps. “And if they don’t know how to do it right now, they’ll throw it at developers, and they’ll come up with a solution to make it happen.”
That is what lets a small team take on a project like this without bringing in consultants. To read the full story, check out the Cat Pumps case study.
Db2 Web Query replacement: Common questions
What replaced IBM Db2 Web Query for i?
There is no single official successor. IBM i shops that ran Db2 Web Query have moved to a range of tools. Cat Pumps replaced it with m-Power, a low-code development platform from mrc that handles IBM i reporting over existing data, including the scheduling and Excel export functions Db2 Web Query did.
Can a small IT team migrate Db2 Web Query reports without consultants?
Yes. Cat Pumps converted more than 300 Db2 Web Query reports with a 3-person team and no outside services engagement. A working knowledge of SQL and the underlying database makes the conversion faster, and vendor support that will step in and help if needed.
Does a Db2 Web Query replacement require moving data off IBM i?
It should not. Tools like m-Power run directly over your existing databases, including IBM i, on-premise or in the cloud. The data stays where it lives, the way Db2 Web Query read it, so there is no separate data migration project.
What happens if I keep running Db2 Web Query past the support cutoff?
The tool still runs. Patches stopped, compatibility with newer IBM i releases is not guaranteed, and there is nobody on the vendor side to call when something breaks. Some shops are still on Web Query for that reason, and it works until it doesn’t. Just be aware that a new IBM i release could break compatibility.
What skills does my team need to migrate Db2 Web Query reports?
SQL fluency and a working knowledge of the underlying database matter more than experience with any specific tool. The migration is mostly the work of re-creating report logic in a new environment, so a team that knows its data tends to move faster than a team that knows the old tool.