IBM Db2 Database Reviews

IBM Db2 Database is a relational database and we use it for all our company's transaction data.

IBM Db2 Database has good performance.

The solution could improve by providing more integration.

I have been using IBM Db2 Database for approximately three years.

IBM Db2 Database is stable.

We have not had an issue with the scalability of the IBM Db2 Database.

The technical support is good.

I would recommend this solution to others.

I rate IBM Db2 Database a nine out of ten.

We are partners with IBM and I'm for implementing Power systems with DB2 in this company. 

We propose DB2 and other IBM products to our customers.

As with all IBM products, I like the reliability of this solution. Db2 is a robust relational database with great features. 

If you're already an IBM Customer or you use IBM products, you know they're powerful products.

 IBM recently purchased Red Hat and things are working more smoothly since then, there's more integration.

I think they need to improve the GUI and I'd like to see more integration with other platforms. 

If you have a project involving several platforms or databases it's the integration with other products that's crucial. Db2 has this capability but sometimes there are issues and you have to contact support to get things fixed. 

They haven't done extensive testing with integration; they'll often send you to third parties. It often means that you have to purchase additional products in order to integrate with other platforms and that's an additional cost. 

I've been using this solution for over 20 years. 

The solution is stable. 

The solution is very scalable. IBM has a mid-range and a mainframe system, so every product is made with scalability in mind. 

Their main target is medium and large size business so they're not interested in small business. 

The initial setup is very easy. 

There is an issue with IBM licenses pricing which is expensive, and it's the main downside of buying IBM products or databases.

I rate this solution an eight out of 10. 

We use the solution as a database that connects to some legacy mainframe systems.

The solution is a very stable relational database and has integration with legacy systems. It is a great product.

The solution could be more modern and have updated database technology. This would allow it to work with modern applications a lot more seamlessly. You will find that there are other better-suited databases where you can deal with more modern type applications.

In the future, they can improve by being closely aligned with the next generation of application that are arriving or that will be developed.

I have been using the solution for a couple of years.

I have found the solution to be scalable.

In my experience, the solution is able to be scaled vertically, but not horizontally. Everyone is using the solution in our organization.

The support we have received has been good. However, the support in South Africa has not been as good.

The installation on our side is automated, we can have a database up and ready within a day. Since we have started using automation, the installation has been very easy.

We did the deployment internally and it was not difficult but it could be for someone that is not familiar with the solution. We have eight technicians doing the deployment and maintenance of the solution.

There is a license for this solution and we pay every three years.

I would recommend this solution to others if they have the proper application, otherwise, it might not fulfil their needs. We plan on using the solution in the future.

I rate IBM Db2 Database a seven out of ten.

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.

Db2 is our primary database for applications in our two data centers. We have a large number of financial transactions that happen every day, and Db2 handles our transaction management.

The asset properties are solid.

The replication is being done well. We have two data centers and the replication that they provide has almost no lag. The maximum lag that we have seen in the past two or three years is one second.

When something goes down, the recovery process is very good.

We are dealing with millions of transactions a month and the performance is very good.

The management is very simple.

We need to have a cloud-based version of this database.

It would be helpful to have a hybrid data storage facility that includes NoSQL technologies.

I have been using DB2 for the past ten years.

We have observed some glitches with the database when the amount of data is growing quickly. This is why we are moving toward a microservices architecture, where each service has its own database.

At this time, because our data is growing, the glitches are frequent.

We have about 4,000,000 requests daily.

We have had contact with IBM for technical support and they are good. Most of our products are from IBM.

I also have experience with Oracle.

The initial setup is complex and not easy to do. It was handled by the database administrators so I do not remember exactly how long the deployment took.

We have an internal database team who took care of the deployment.

We are currently in the process of migrating some of our models to the cloud, and we are looking for a cloud-based relational database.

The suitability of Db2 depends on your environment and needs. If you want to implement an on-premises monolithic application that can handle all of your transaction management then Db2 is a good choice. 

The technical support is very good, and if you have multiple data centers, the applications are also good.

I would rate this solution a seven out of ten.

The primary use for our Db2 database is for OLAP (Online Analytical Processing). Our department is using it for data warehousing and data analysis.  

We are deploying some of our enterprise systems to Azure. We would like to migrate data there and most of the systems will be running on the infrastructure as a service, so we will have lots of servers. Migrating data from Db2 becomes an important matter.  

Our target currently is to create the infrastructure which would include the servers, the backup solutions, the databases, application servers and whatever else we need.  

Db2 enables us to analyze big amounts of structured data in DataWarehouse solutions.

The feature that is one of the most valuable in Db2 is the DPF, or the Database Partitioning Feature that use Massive Parallel Processing architecture. We have deployments where one database is deployed on multiple physical servers. It is not exactly like RAC from Oracle. The purpose is not the availability but the performance and scalability of the DPF.  

Integration with other services could use some improvement. Currently, we are using Informatica ETL (Extract, Transform and Load) and the data is not loading as expected between the Db2 database and Informatica. Our goal is to eventually migrate the data to Azure servers and evaluate how it will perform. Currently, we are doing a POC (Proof of Concept) on this migration, but the second step cannot be completed without a dependable data load.  

We have been using Db2 for a long time. Maybe 15 years.  

DB2 is very scalable offering multichoice of possiblities - massive parallel processing and also  clustering.

We have technical support from IBM. If I had to evaluate their services, the quality really depends on the person that gets the ticket. There are some very good specialists on the technical support team and some that are not so good.  

If the ticket is critical, it will go to a queue and the IBM team will help you out very quickly and efficiently. Of course, sometimes critical problems are difficult and take some time to resolve.  

If I had to rate technical support overall, then I would give them about an eight-out-of-ten.  

We are a typical enterprise with the typical array of databases. Primarily we use Db2 and MS SQL, and some others. We have reporting tools like Business Objects, Power BI and Micro Strategy. We also have data warehouses. So we have ETL tools and then we need to have the backups, scheduling, and monitoring. We are using more than one database type for different reasons, so it is not exactly that we have switched away from something else to Db2.  

The initial setup is straightforward. I think that installing the Db2 is not that complex and it should not be a problem for a skilled DBA.  

Usually, we use our own team to maintain our products and we do not require outside services from vendors.  

As we have experience with a variety of database types any one of them could play into our architecture. I was hoping to have PaaS backup solution for the Db2 that we plan to deploy to Azure. But current plan is to back up the Db2 database to storage instead to some service in cloud. Doing it this way we would need to do a work-around and manage the backups by scripting and manage the retention and the sizes and disk drives. It is not optimal and it would be better if we could just send the backup to some kind of API or service in Azure and just configure it to back up images and files. In our testing, that is currently not working with Db2.  

I was looking for this kind of migration solution for the Db2 database, but I could not find it — which surprises me. I looked at the Tivoli Storage Manager, which supports the Db2 backups to the API, but they do not have that kind of PaaS service in Azure.

I have experience working with both Oracle and Db2. Comparing the two products, I would recommend Db2. Both Oracle and Db2 have some unique features that separate them. Although they are different, in comparing the two databases, they are both enterprise grade databases with lots of good features. But from my point of view, Db2 is much better.  

On a scale from one to ten where one is the worst and ten is the best, I would rate Db2 as an eight. It is not rated higher because I think that there are things that can be improved. It is currently not perfect. The graphical tools are not good. It is very common for GUI interfaces in IBM products to be lacking. For the first-time user who has no experience with it, the GUI will not seem very straightforward. If you had to work with it for four years, then you get used to it. But for the first-time users, it is not that user friendly.  

If some of the user-interface features can be enhanced, it could be a nine. Db2 is a good database. It is for structured data and there is always room for improvement. It requires an experienced person to handle it.  

We use the solution as a query tool for requesting and updating data.

The solution has the best querying features.

They should make the process of building up queries easier for the solution.

I have been using the solution for some years.

It is a stable solution. I rate its stability nine out of ten.

Presently, we have 200 solution users in our organization.

The solution's technical support team is good.

The solution's initial setup is straightforward. The deployment process involves requesting access to different test environments and productions. It takes a couple of hours to complete.

We implemented the solution in-house.

The solution is intuitive and easy to use once you know how to build up queries. I rate it a nine out of ten.

Some customers use it for imaging databases, and others use it for ERP systems.

The most valuable features are the HADR, and it is so simple.

The backup solution lacks flexibility in some situations and could be improved. In addition, the management tools should be improved in the next release.

We have been using this solution for more than five years. We mostly use version 10.5 but sometimes use version 9.7.

It is a stable solution.

It is a scalable solution. 

I rate the technical support an eight out of ten. Our issue with the technical support isn't isolated to IBM Db2 Database, but it is an IBM policy. They try to solve problems remotely, but it is not the same as other products because it takes more time to solve.

The initial setup was easy. I rate the setup an eight out of ten.

The solution has annual licensing, and the costs are reasonable for the product. I rate the pricing a six out of ten.

I rate this solution a seven out of ten. I would recommend this product to customers. Most solutions have some environments requiring an enterprise database, so if a customer uses an IBM solution, the database should be Db2. Some customers may be using SQL Server, and if we have the solution for the Microsoft environment, we will recommend them to another database. But if the proposed solution is AIX or Unix system, we recommend they use the Db2 database on that platform. So it depends on the environment.