Share your experience using IBM Db2 Database

The value and impact of using IBM Db2 Database lie in its essential role in storing data. The benefits include enhanced performance, reliability, and effective data management compared to other databases.

The most valuable feature of IBM Db2 Database is its ability to perform automatic self-management, reducing the need for manual tasks such as managing logs and folders.

One area where IBM Db2 Database could be improved is its Java development environment. Similar to those found in competitors like Oracle, there could be more user-friendly tools with features such as drag-and-drop functionality, visual basics, and low-code capabilities.

We have been using the IBM Db2 Database for ten years.

The platform is stable. I rate the stability an eight out of ten.

The primary concern is related to the cost implications when scaling with multiple nodes in a database. The associated costs increase when additional nodes are added, each requiring separate storage space. We have approximately four or five Db2 instances being used in the organization.

It is a scalable platform. I rate the scalability an eight out of ten.

I have used MySQL and Oracle in my previous environments. We switched to IBM Db2 Database for auto-management features and reduced manual intervention.

The initial setup is straightforward. We have to install and register. The deployment process includes downloading the software from the vendor's website, having a customer account, copying the downloaded file to the machine, and executing the installation. It takes five to ten days to complete. We have around 50 executives working in the database administration team.

We implemented the product in-house.

We purchase the product's yearly license. Later, we have to pay support and license renewal fees. Its pricing is comparable to other database solutions such as Oracle and MySQL. If you choose to buy IBM Power Systems, there may be opportunities to receive Db2 licenses at a lower cost or even free of charge. However, if the installation is on servers other than open Power servers, standard licensing fees apply, similar to those of other database solutions.

The application has analytical tools to support day-to-day management and analytics needs. It is convenient to meet business needs objects.

Regarding integration with other tools and systems, Db2 can be integrated with comprehensive banking solutions involving various teams, including CVS, analytics, and importing teams.

As for recommendations for those considering Db2, it can effectively impact performance. If an organization predominantly uses Db2, individuals are more likely to choose Db2. However, there is a challenge related to training resources for Db2, which may be less readily available or focused on compared to other platforms like Oracle.

I rate it a nine out of ten.

In my current project, where we're taking information from an old IBM mainframe and using Db2 to convert those checkups into GRP (Government resource planning solution).

We have a transaction server, Db2, that already exists in one place. We have our own solution using Oracle. So, from this transaction, we're taking information from Db2. We're running about the engine, that is, the various queries. And they're taking the information into our Oracle server. That's the way we're cleaning and fine-tuning the information taken from one system to our system. And that system is Db2.

We are using our own developed workflow management system. We're working mainly for IMF and World Bank with Asian Development Bank. Based on the aids, they're giving in that particular workflow, we define the process needed for any country receiving aid.

We provide the solution to any government's finance department in any country. So, in team mode, they previously had the IBM solution. We're using our GRP solution, which is a public finance government resource planning solution. We need to use the existing system. On top of that, we're providing the vendors and information to the public regarding the aid they're getting from that department.

So it's like a combination of solutions using various components to provide the solution in GRP from the existing IBM solution.

This is the solution developed for IMF, where whatever funds they're giving to a particular country, all the grants are coming from the IMF using the Db2 server. So once they transfer the amount, the information comes into Db2 against a particular project, like for education or healthcare. 

So, the IMF grants a specific amount for a specific project in a country. Now, that country likely has various projects running under that department. Our GRP system manages those projects for that particular country. We take the base information – what money is coming in – and based on daily transactions, we update Db2 database to report back to the IMF. This report details all expenditures, including who approved them and which ministry was involved.

So, IBM Db2 database has been particularly effective for the data management requirements.

Db2 database scalability and performance capabilities match our database needs. It covers pretty much everything a database administrator or engineer might need.  

Db2 is a full-fledged setup. The database is just there, ready to handle whatever you throw at it. 

IBM Db2's reliability and uptime have contributed to the business continuity planning. It's been highly reliable.

Db2 interface could be improved a bit. Comparing it to Oracle, Db2's interfaces could be improved. 

I have been using it for more than two and a half years. 

It is a stable solution. It offers good stability. 

It is a very scalable solution. It offers very good scalability. 

We have access to 24/7 support. The customer service and support are very good. 

Positive

Db2 excels in handling large datasets. But Oracle is strong, too. I can't definitively compare which is better, Db2 or Oracle, because Db2 integrates seamlessly with existing IBM solutions by design. That's their database, after all. 

Typically, we use Oracle in conjunction with Java and their mainframe systems, specifically their ERP systems. So, each has its own merits. It really depends on our specific needs and the features required for either the core government solution or our own custom wrapper. Honestly, it's tough to declare Db2 or Oracle inherently better based on features alone.

The deployment time and complexity totally depend on the solution we're implementing during this initial setup. It could be for one organization, maybe three or four. For another organization, maybe a seven or eight. So, it completely depends on what type of setup you want for the specific organization.

Where I work, the deployment model is always on the government's premises or their government cloud. It's never on public cloud platforms like AWS or GCP.

Recently, we did some data center migration. It's not a quick job because it's government resource planning. We need to involve all the ministries in the data center, which requires a complete plan.

Last time, it took around two and a half months, ten to be exact, for me to roll it out with my whole system team involved.

I would rate the pricing a five out of ten. Since it's a government contract, the rates are negotiated and agreed upon with the government. So, it's not like the standard market price. It's not super expensive, but also not cheap.

When it comes to Db2, integration is key. We integrate through various engines, and each engine integration requires both parties to have a communication layer, which we configure.

Overall, I would rate the solution a nine out of ten.