IBM Db2 Database Reviews

We work at the banks. The bank has many IBM products. IBM Db2 Database is just one of them. It is mostly mainframes, but there are still some relational databases, such as IBM Db2 Warehouse, that we are interested in purchasing for financial companies.

Because we are a big client, we have a good price with IBM Db2 Database.

Based on my use case and understanding, performance-wise, Oracle is probably better because they may have better technology. However, for us it is acceptable since we do not use it extensively, so there is no real difference for us.

We mostly use the core Oracle database.

IBM Db2 Database is perfect and leading in this area.

Regarding how IBM Db2 Database can improve, I do not have anything in mind as our use cases are not complicated. There is PostgreSQL and SQL Server available. IBM Db2 Database, because of enterprise performance and support, is why banks still maintain their relationship with it. I am uncertain whether other companies do the same, but banks do.

The IBM Db2 Database in our organization is used for diverse industry clients, including the banking and entertainment sectors. The solution has been used for OLTP and warehousing in our company. 

The optimizer plan feature of IBM Db2 Database offers great value. At our company, whenever we check access to a particular query, the aforementioned features assist us internally by providing a suitable plan. The newly added feature of ALSM is one of the top features of IBM Db2 Database. 

IBM Db2 for zOS serves as the central database for all the core business applications in the two banks I work with. All applications use Db2 as a data server. We fully implement and utilize most of Db2's functionalities and capabilities for core banking business applications.

IBM Db2 has integrated well with open systems and additional applications on the zOS platform, providing a robust DB service for all core business applications. It offers great stability and scalability, which has positively impacted the operations.

We continued with our existing mainframe Db2 solution due to its high availability and the ability to maintain an active configuration across multiple servers or LPARs.

There are two versions of Db2. One is Db2 for z/OS. The other is Db2 LUW—LUW stands for Linux, Unix, and Windows. From an availability perspective, it's not on the same level as the z/OS version, which I consider superior. This is why major airlines, banks, insurance companies, and retailers worldwide rely on mainframes and Db2.

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.

We use the product for managing large volumes of data, particularly in mainframe environments. It supports interoperability with other IBM systems and products.

They could enhance the product's cloud integration and general-purpose database capabilities to better compete with solutions like Oracle and Microsoft SQL Server.

I use the IBM Db2 Database for development applications. Many clients in our company have business applications currently working on it.

The IBM Db2 Database is trusted, and IT effort is less than any other product. IBM Db2's support for both structured and unstructured data benefits me because both are allowed.

IBM's impact on in-memory technology is good for working in our organization. The IBM Db2 multi-workload helps me manage diverse business applications with easy management. We just have a backup of incremental changes every day, and applications working with it do not need maintenance gradually.

The IBM Db2 Database brought benefits to my organization as we did not spend too much money on security. It is secure enough, and the IT teams do not have heavy work.

The data resides in Db2, and the application is linked to Db2. My job is to pull the data through the Talend tool from Db2 and load it into Snowflake. At the Snowflake level, I handle the data for reporting purposes.

Db2 is an on-premises solution. I only use SQL over there. It's very easy to figure out how the data is present. I can check what the keys in the table are. I can easily export that to further work on it in Snowflake. For data modeling and other tasks, I have to pull the information from Db2.