IBM Db2 Database Reviews

We are a bank. The banking system uses IBM Db2 Database to save data in the database.

I have found the most valuable feature to be its availability. There is almost no downtime and the performance is very good.

I would like to see some artificial intelligence brought into the solution. Additionally, we need a way to gather some reporting information from the bank.

I have been working with IBM Db2 Database for a year now.

There are no real issues with the overall stability of IBM Db2 Database.

We do not have any problems with scalability. I would say give high marks for scalability.

Technical support is excellent. I would like to see better documentation. We have to speak to a support representative when we can not find the documentation on an issue we are facing.

From a performance perspective, I prefer SAP HANA for performance.

I would recommend IBM Db2 Database as a ten on a scale of one to ten. It is very powerful and responsive. 

The primary use case of the IBM Db2 Database is our trading platform.

We use store procedures and SQL. 

We have some tables with partitions, as well as some tables with a large amount of data. 

We use partitions, we use views, and we know who uses them.

We don't have any compatibility issues because we use all IBM products. We use every IBM product. That is why we use IBM's developer tool as well. We never encounter any product compatibility issues during development and deployment.

That is one of the good things that happened to us, in my opinion.

When we had server-related issues, such as a database outage, compatibility and support were good. I believe that because the support is good, they jump in and assist us in determining the root cause. 

The product is really reliable. 

We have seen very few instances of problems, overall IBM products are valuable.

The most valuable features are compatibility and support. 

I am currently moving away from that core application. I am not focusing on the solution. 

It is our trading application, and there are some reservations, about continuing to upgrade to the latest versions even though we are currently running on older versions. I believe the first step would be to upgrade it to the most recent versions and then see if any improvements are required while continuing to provide feedback on older versions.

The pricing could be improved, it's expensive.

I am not working on it as closely these days, but our application began in 2001, and we have been using the IBM Db2 database since then.

IBM products are very nice and perform very well.

IBM Db2 Database is a stable product.

We use a scalable WebSphere Application Server topology, but it's a monolithic application that can only be scaled vertically, not horizontally, because it's a monolithic single database, but those limitations exist. But there are times when I believe we are pleased with the product.

We have multiple production environments and various resources, as well as separate teams to manage the database and separate teams to manage the Application Server. I believe it began with a small team, but as time passed, I believe the number of environments and teams increased. Teams are popular now. I believe we have teams dedicated to each area.

I can say that there are approximately 100 developers, both offshore and onshore.

We have support. In my opinion, they are prompt, we receive responses from IBM within two to three hours. 

There are some challenges. There may be one or two instances where it exceeds, but we are content with that.

The product is very reliable and stable, and we used to receive prompt responses from IBM on support. 

Previously, we were using the WebSphere Application Server. Those applications are in maintenance mode.

We also worked with the Application Developer,m which is the Rational Application Developer for WebSphere software. It is running on legacy Java version 8.

No one is currently using this software because everyone has upgraded to the latest version, but our application is still running with an older version. I don't believe anyone is currently using the older version of Java and the Application Developer that we are.

It's an older version of Java, and I don't believe any developmental improvements will be made to the tool as of now. Because we are not using the most recent version of the tool and the most recent version of the WebSphere Application Server, the feedback I could provide may be ineffective.

We are in the process of migrating to the AWS Cloud.

Our design approach is to convert our monolithic applications to microservices.

We have not used Hadoop, High-Availability Clustering, or Backup and Recovery, we only use the Application Server to host our applications.

The monolithic application is hosted on-premises.

We installed the system in 2001 and have been using it ever since.

The maintenance and support staff is quite small. We have a dedicated database team, we can support multiple database products in addition to Db2.

I am aware that IBM pricing is expensive in comparison to other products. 

However, I am not the person who dealt with pricing.

It is expensive when compared to other products.

We are moving away from IBM products.

Everyone is now gravitating toward AWS and cloud computing. And this is a legacy monolithic platform. My advice will be ineffective. The legacy system was designed in the year 2000.

When we first launched our product, IBM hosted our client platform.

Our client insisted on using IBM products, but I believe we are now satisfied. However, the company where we started, has now been acquired by four different companies.

We are working on a different company that has Java-based products, department-based products, and many other products. It's obvious it's a trade. We will build a trading platform on which our clients and sponsors will trade.

I would rate IBM Db2 Database an eight out of ten.

It's shipped with another software IBM product called Maximo. I'm using it just as an underline. It is a typical database. I use it as a database container.  

The setup process has become much easier recently. 

It is quite stable.

The solution can scale well. 

I am not heavy into developing in Db2. All my development is in the application itself, not in the Db2. Therefore, it's hard to think about areas it needs to improve in. 

The user interface is not user-friendly. There's a converter tool that is much easier for us in comparison. 

We would like the product to have tutorials and answers to questions and troubleshooting to be easier to find online. It's hard to find the answers you're looking for. 

I need data replication to be much more efficient than what is available in the current version. 

I've used the solution for around three years now. 

The solution is stable. Even if there are a large number of records, the performance stays the same. There are no bugs or glitches and it doesn't crash or freeze. 

We have found the solution to be scalable. If you want to expand it, you can. 

We don't really have individual users. It comes as part of a package and therefore it's hard to say who is using it and who isn't. 

They need better support and better online resources. If I try to Google something to troubleshoot, I cannot find an accessible answer. 

Neutral

The initial setup has recently become easier and more straightforward. A lot of enhancements have happened here. Still, it is a bit complex. 

I am not paying the license for it individually. It's included in the package.

That said, the cost in general could be more reasonable for the package as a whole. 

We did look at other options and found them to be more reasonably priced. 

I'd recommend the solution to others. However, I'd recommend other potential users try to find a cheaper option. I'd rate it overall at a seven out of ten. 

I'm using this solution for a financial network. I make and prepare the databases for analysis.

I'm using version 11.5. There are 1,200 people using this solution in my organization. It's deployed on-premise.

It's very secure.

The command line part of this solution could be much better. Redshift is a lot better. It's easier to work with them. IBM Db2 is a little bit outdated.

I've been using this solution for two years.

It's scalable.

Technical support isn't very helpful when I've had problems.

It's not easy to set up. It takes a long time, especially compared to other solutions.

It's very expensive.

I would rate this solution 6 out of 10.

We are using it for our SAP system.

Db2 Database has given us good results since we have started to use it. We predominantly use IBM hardware, and this is one of the reasons why we started to use Db2 Database. 

Db2 Database has a very good HADR capability. High availability resilience is also good in this solution. It also has pureScale, which allows you to upgrade one node to get very good and high-level resilience. If you are using a database on five nodes, you can take one node down, upgrade that, and let that node up. You can then bring the second node down, upgrade that, and so on.

The only drawback that we see in Db2 Database is the crash recovery. When there is a crash and somebody has to do the recovery, Db2 Database first stops, and then it does any crash recovery. In Oracle Database, crash recovery happens within the database. The database is not shut down.

I have been using this solution for five or six years.

Initially, there were hiccups, but now, it is a robust database. The only limitation that we have found is crash recovery. In terms of bugs, every database will have some bugs that will hit you. I don't see much in terms of bugs in Db2 Database. Whatever known bugs are there, we get those issues.

They are really very good. Overall, if I have to give a rating, I will give them an eight and a half or a nine out of ten. Their response to our requirements is quite good. They have good resources at the technical end. They take us very seriously. It might be because we are one of the largest accounts. I don't know what happens with medium-scale industries or small-scale industries. 

We migrated from Oracle Database to Db2 Database because it was quite a good and cost-effective solution. Oracle Database was coming out to be expensive.

The initial setup was complex altogether. It was complex because we were moving from Oracle Database to Db2 Database. A lot of code changes were required. 

We did not buy it. It came with our hardware without any complimentary maintenance. If I compare Db2 Database with Oracle Database, its price is lower than Oracle Database.

I would recommend Db2 Database to others because, as time passed, they have made a lot of changes, such as crash recovery. The time of crash recovery is reduced by almost 60% to 70%. Db2 Database also has Db2 BLU, which actually is in-memory. We have not explored this particular feature, but I would recommend others to explore it. With Db2 BLU, it becomes equivalent to HANA. We are seeing it being used a lot in large banks etc.

Among Oracle, Db2, and SQL databases, I would rate Oracle first, Db2 second, and SQL third. I personally believe Oracle is the most robust database. Db2 is the second robust database.

I would rate Db2 Database an eight out of ten.

We use the solution as a database for e-commerce applications.

The solution's most valuable feature is scalability.

The platform itself needs improvement. They should develop a containerized version of the solution. In addition, they should include dashboard features as well.

We have been implementing the solution for customers since 2006.

It is quite a stable solution. I rate its stability as an eight.

We have 34 technical users and over 50 end users for the solution. I rate its scalability as an eight.

The solution's technical support team could respond faster.

Neutral

I have used Oracle in the past. In Comparison, IBM provides better performance and scalability features.

The solution's initial setup process has medium complexity. It takes a few days to complete. I rate the process as a seven.

I rate the solution as a seven.

We use IBM Db2 Database to monitor the deadlock's thread pool status of a particular DB or the particular process or whatever the corresponding DB instance is. We do this for the customer's requirement.

The most valuable feature of the IBM Db2 Database is security.

 I have been using IBM Db2 Database for two years.

IBM Db2 Database is stable.

I have found IBM Db2 Database scalable.

The technical support can be faster.

I have not used other solutions in this category other than IBM Db2 Database.

The initial setup of the IBM Db2 Database is straightforward. The full implementation took approximately one month.

We did the implementation of the IBM Db2 Database in-house.

I would recommend this solution to others. If some planning is done and things are in place then the solution will work as expected.

I rate IBM Db2 Database an eight out of ten.

Db2 is mainly used for Core Banking Systems, credit card systems, and production systems for CBS collecting.

Db2's best features are that it's self-maintaining and self-monitoring, which means I have to view and monitor the database far less often.

There are some issues with Db2's database file system not being readable. The storage could also be increased, and the monitoring could be improved.

I've been using IMB Db2 Database for nine years.

There were a few hiccups directly after installation, but Db2 has been very stable since then.

Db2's scalability is very good, especially when used in the IBM power system.

The initial setup was very straightforward.

I would rate Db2 Database eight out of ten.