IBM Db2 Database Reviews

We use it to provide for back-end DB for many proprietary applications. The most valuable features are reliability, performance, and portability across different platforms.

We have moved a lot of our applications off zOS to distributed platforms and IBM UDB DB2 has been extremely critical in our solution to provide for a scale-able, cost-effective and reliable DBMS solution on distributed platform.

The other advantage is we don't have to make lot of changes in the application DB2 access layer in order for it to work with IBM DB2 UDB. These applications have been originally designed to work with the host database (IBM DB2 zOS).

I would definitely like to see a better interface to interact with the database. Performance monitoring tools which come out of the box don't need to come along with all the bells and whistles. They need to be effective and intuitive. There are ways to do that out-of-box even today, but it can be improved

We have used this solution for over 15 years.

There were no issues with stability.

There were no issues with scalability.

The IBM Technical Support model is satisfactory.

We used XDB (Micro Focus RDBMS equivalent to DB2) which used to have scalability and reliability issues in our development environments. We switched to IBM UDB DB2 in our DEV environments on account of its reliability and scalability.

The setup was straightforward. However, the Linux setup can be improved.

I love the way the product is licensed on zOS and zLinux (core-based). However, IBM needs to improve their licensing for cloud environment, as we are planning to leverage that platform extensively in the future. Right now, the setup for AWS/Azure licensing is very confusing and not cost-effective.

We evaluated Oracle, but the ease of application re-hosting with IBM DB2, as well as its comparable reliability and scalability tilted it in favor of IBM DB2 UDB.

For folks looking to re-host applications that are using zOS DB2, our advice is to strictly go with IBM UDB DB2. Do not consider other options, as they usually require extensive changes in the application layer.

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 solution is a major central relational database management system that maintains all of the data for our bank's core business.

The availability, reliability, consistency, security, performance, and methodology of the solution are all excellent. It's a proven product for many, many businesses in many, many different areas. It's probably one of the best products on the market.

The self-management and optimization features are probably the best on the market.

The ease of use, or ease of management, could be improved.

There are many improvements all the time on the solution. There is no one thing that I would mention. IBM invests a lot of money to improve the tool and maintain it. There are improvements all the time happening in different areas. 

I've worked with IBM products since 1989.

The solution is stable. No technical issues have ever occured.

Technical support is good.

The initial setup is quite complex. Nothing is simple on the platform. Deployment times depend on the extent of the organization. Different tests need to be done: unique tests, integration tests, user acceptance, performance, etc.

There are specialists on-premises that work for the bank and they handle everything themselves.

We use the on-premises deployment model.

The solution is suitable for big organizations, big financial institutions, government, ministries, the army, insurance companies, etc. It's not for small end-users.

I'd rate the solution nine out of ten.

The learning curve for the Db2 specialist is high. To become a specialist, under production level, takes two years. It's a complex product.

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.

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.

In terms of improvements, IBM Db2 can improve its interface and its functionality. Also, the embedded functions should be much richer than the current ones - the functions which are embedded in the engine itself.

For example, I can find more DEPTH functions in Oracle than in Db2. Also, SQL Server still has richer functions than Db2.

I'm working with Db2 for two years now, since we migrated to the Cloud and converted from the SQL Server.

I work with Db2, SQL Server, and Oracle.

I'm a specialist in the product, doing support. I received special training for it.

In terms of stability, I have some issues, but I cannot figure out if this is due to the database or the platform in the engine itself.

Additionally, sometimes I find the response is not good, meaning a reasonable response time. For a while the team was working fine in another engine. What I look for is the design and whether the syntax is different. I don't know. I'm really not certain about the holes.

Since it's on the Cloud, it's pretty much scalable with no limits.

We did get a specialist to help with the setup and deployment to the Cloud.

IBM Db2 was much cheaper as a package than using other products. This is because IBM supplied a package with its product. It's an application. So it was much more efficient and a stronger competitor in that regard.

Performance-wise, Oracle is the best solution. It is much more reliable. Regarding the end user administration and the functions available, SQL Server is much easier.

They have much more user-friendly interfaces. Regarding Db2, I'm a little bit in doubt. I don't see that it is significantly different when I went from SQL Server to Db2. I have not seen any significant improvements or changes.

The advice I would give is to have a good administrator. Have an administrator that is skilled in that field so he can tune the database's performance and understand the know-how of how to administrate that platform.

Overall, I would give IBM Db2 a 7 out of 10. 

For it to be higher, it needs a better interface. It is very important to have. I am very keen to have such an interface.

We are not using this with other users, it is dedicated to our backup solution.

We only have one instance, one user, one service, and we don't have any other users or clients that we connect to.

A database system is a tool used for reporting and to monitor if it is running or if there are any issues. We can set alarms and warnings. It is a backup system that manages the backup.

The most valuable feature is that it is robust. We had a crash of the backup system and the IBM DB2 was always up and consistent. It's robust, and for us, it was always up and running.

The database is deployed using the command line, so we did not test any other tools, aside from DB2 using the command line interface.

Because this solution is a big data database only dedicated to the application server, it is very difficult for us to assess areas of improvement. We use the database, so we don't have any other requirements or need to use it in any other way.

The licensing fees can be reduced. While we don't see the breakdown, we know that IBM licenses for the backup system are very expensive.

I have been working with this solution for ten years.

This solution is stable.

We don't have experience with scalability because the server is also a dedicated server and the physical hardware has always been dedicated from the beginning. After five years, we made a technical upgrade and have been the same since.

My colleague has the primary responsibility for the backup system and he has had to open tickets on two occasions. Each time, they were okay and the issue was resolved. 

The initial setup is simple and straightforward. It's easy to install with no special configuration for a big data database. They make things simple.

It took less than an hour to deploy.

The cost is embedded in the price of the backup solution. We know that the backup solution is quite expensive and with each inside license, there is also a database license.

We don't see what the specific price of the DB2 license is because we pay for the backup license as a package.

This is a robust and stable product but it's expensive.

I would rate this solution an eight out of ten.