IBM Db2 Database Reviews

We work with a few use cases suggested by the IBM Watson Library. All the data is inside the event processor, we can extract it with a query. There are multiple use cases already in the IBM marketplace.

It's easy to search and extract data from the warehouse using queries.

The queries can be difficult for beginners because there are so many. I would like to see more use cases for flow analysis that enable us to correlate the flow with events. Adding this feature in a QI format would be good for beginners.

I have used Db2 for around two years.

I rate Db2 eight out of 10 for stability. 

I rate Db2 nine out of 10 for scalability. We have more than a thousand users. 

IBM's technical support is excellent. They provide a solution in 24 to 48 hours. 

Setting up Db2 is straightforward. Most IBM products I've used aren't complex to integrate or deploy. We deploy it on-premise and in the cloud.

I rate IBM Db2 two out of 10 for affordability. It's expensive but not much more than other tools. There are also cloud-based solutions like Elasticsearch. 

There are multiple competitors like Oracle, but Db2 is the best for our use case.

I rate IBM Db2 nine out of 10. It's more expensive, but it's better than the competing solutions. I have to deduct a point for license costs. Everything else is excellent. We recommend Db2 to many clients, but few adopt it due to the high price tag. If a project has strict budgetary restraints, we typically don't recommend Db2. 

It is installed on the mainframe that we use for our applications.

It's the best solution in terms of security, performance, and availability because the system is available 24/7.

The problem with this environment is that any software that you install is very costly because there are no free tools for this environment.

The environment itself comes at a very high cost because the mainframe machine is very costly, and the licensing cost is very high as well.

I've been using IBM Db2 Database for the past 22 years.

It's very stable, and the performance is very good.

We use IBM technical support for the big bugs related to the operating system and the database. We haven't faced any problems with the database. Sometimes, with the operating system we need some fixes, and technical support has sent us those. On the application side, our team develops the application and solves any problems related to it.

Previously, we used COBOL with a database sold by Computer Associates. We didn't have lot of choices for mainframes at the time. The best database that can run on the mainframe is the IBM Db2 Database, and we have stayed with Db2 from 2000 to the present.

The initial setup was quite simple because we've been working in this area for more than 40 years.

It took about a year and a half to develop and deploy the whole application.

We developed the application, and we deployed it using a solution strategy. We have an IBM partner who gave us all the software that we needed, and we implemented it ourselves.

We had three system engineers, two people for the database, and two people for the application.

Our ROI is big because we earned about 100 billion in our currency.

It's very expensive for West African countries like ours.

We are currently in discussions with IBM concerning the reduction of licensing costs. We have a license based on the capacity of the machine and are looking into a license based on usage.

There weren't a lot of choices for mainframes at the time.

If you're going to use it for the first time, you would need lot of training and some technical support. You would need support during development as well.

I would rate this solution at nine on a scale from one to ten.

We use it for the core banking business. We have Db2 for z/OS 2.4 on the IBM mainframe machine. It is on-premises of one of the big banks in Israel.

Its robustness, scalability, availability, and performance are valuable. All these are the major attributes of a relational database for supporting a very high-volume business, and Db2 is very good in all those areas and in all those attributes.

They should simplify the management of Db2 as a relational database system. There should be the simplification of management. This is probably one of the most important asks for being successful in the future.

They should add AI support for performance improvements for application and system performance and tuning management. AI is a very deep and complex product. There are thousands of parameters, and it is very hard to do it manually. So, I would suggest developing an AI system to do the monitoring, tuning, and performance improvements.

I have been using this product for 40 years.

It is very stable. There are organizations where Db2 has been working for more than a year and sometimes, for many years without going down. The operating system as well as Db2 work for a long time. There is no downtime at all.

It is very scalable. There are about 250 application systems with even more different databases on the same server with data sharing.

Their technical support is okay. It was better 10 years ago, but it is still okay.

It must be done by a professional. It is not a simple task. Somebody with quite significant experience must do the initial setup. It is difficult.

It is expensive.

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

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.

The user interface is old and needs to be improved. It doesn't match the responsive and suggestion-rich UI of cloud solutions. New functions don't come to mind.

I have been working with Db2 for around one and a half years.

In terms of stability, I would rate it as seven out of ten.

Scalability is not always good in on-premises solutions. I would rate it five out of ten. The difficulty in scaling on-premises solutions is one reason we moved to the cloud.

I used Postman previously, which I worked on when I was involved in mobile development. Now, at IBM, I have switched to the data engineering stack.

The setup is not difficult; it's simple.

Overall, I rate Db2 as six out of ten. I can recommend it if someone wants to go to IBM stack. If someone is willing to adopt IBM's stack, then definitely they will be using IBM Db2.

We primarily use the platform to store query data. I work in a bank, where we store customer information on it.

The product has improved our organization by performing well for data storage and queries. It helps us retrieve information quickly.

The solution's querying feature is most valuable. It allows me to retrieve data quickly.

The solution's data retrieval speed could be improved, especially for heavy queries. Better optimization or indexing might also be involved.

I have been working with IBM Db2 for about two years.

The product is mostly stable, even in a large organization like ours. 

I rate the stability a nine out of ten.

We manage around 15,000 to 20,000 platform users. I rate the scalability an eight out of ten. 

I do not interact directly with the technical support team. 

Our internal support team handles any issues and communicates with the provider.

The solution has been good with strong performance, contributing to our organization's efficiency.

We use the product combined with other solutions, such as SAP Crystal Reports and various reporting tools, but we do not directly integrate it with databases like SQL Server.

I rate it as ten because, despite occasional issues, it performs very well overall.

Our company uses the solution as a database service for a client in the furniture manufacturing industry. 

The solution's security is very tough and impenetrable. 

Hardware and support subscriptions are very expensive. Better partnerships in the Middle East or Egypt could reduce costs. 

The solution no longer supports POWER8. 

I have been using the solution for ten years. 

The solution is very, very stable. 

The scalability is an issue for us because Database Hammer does not work with IBM Power and POWER9 is too expensive. 

Technical support is very helpful and better than competitors such as Dell, Lenovo, or HP. 

We previously used POWER5 and POWER7 so have been with the solution for some time. 

The setup is very easy and we accomplished it through self education. 

We implemented the solution in-house. 

The solution's hardware and subscription model for support are very expensive in the Middle East or Egypt. 

I rate cost a three out of ten. 

Database Hammer does not work with IBM Power or POWER8. It is too expensive for us to purchase POWER9 so we are migrating to AWS and comparing that to Azure. 

Currently, our server and database are shut down and not in use. 

Stability, mobility, and security are rated a ten out of ten but the extreme cost changes my overall rating to a five out of ten. 

I used DB2 two years ago. It's a data warehouse project solution for a bank. I use DB2 as a warehouse and the data stacks for the APL.

My role in this project was as a database designer. I would design the database, the warehouse, and get the requirements. 

I am not detailed in the technicality of creating the table in DB2.

I am now selling this product.

The most valuable feature is data analytics.

The price should be lower.

I have been working with this solution for six months.

I use the DB2 BLU version.

This solution is stable. It's good.

I don't' have any knowledge about scalability.

The technical support is good. They have presales and technical support. When you submit a ticket the response time is quick.

Previously we were using SQL Server.

The main difference is the pricing and implementation.

The initial setup was straightforward.

It took four months to deploy this solution.

I only use one server to implement the solution.

I think that everyone knows that with IBM the standard price is higher than the others.

There is a lot of documentation available. I was, however, able to find what I needed through Google.

For our clients who have a large scale enterprise, we suggest DB2 and mid-scale enterprise customers we suggest SQL Server or others.

It's a better solution, it's better on the application. The purpose of DB2 is for a data warehouse or with data analytics.

I would rate this product an eight out of ten.

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.