IBM Db2 Database Valuable Features
Mainframe Technical Manager/Service Integration Lead at a tech services company with 10,001+ employees
I like that its true active-active. For example, if there are two instances within a cluster, we can take one of them down and there's no failover or switch over. There's no primary and secondary, it's true active-active. We can take one side down and we can upgrade that with new maintenance or a new version, obviously testing coexistence beforehand, without impacting the business.
In a distributed world, you've got lots of different prerequisites you've got to be managing here. Not just the database - possibly the VMs that the database is in and the OS that the database is running on, Linux or Windows, as well as the storage.
I like its high availability. It's well supported by IBM. It's used by a lot of the larger business organizations globally within banking, finance, credit cards, insurance, retail, and government.
We're proving that it's got that high availability and robustness. We can prioritize the workloads that are coming into that database management system, using the features of the IBM z/OS environment. That way, if this transaction's coming in off the network that is in and out, they will be given priority over somebody doing a lengthy query that's coming in from the network that you would consider to have more batch-like tendencies.
We like that it's using separate specialized CPU engines to manage the locking and the sharing of data via a coupling facility. This stays on the CPU that we would be licensed for. We call them specialized engines that you don't license. They're not paying your licensing costs. Whereas, for example, in other database management environments for high availability, they communicate between themselves over an IP network. The CPU would be higher for them. There's no special process or capability that allows taking that CPU and that communication between them. It has to, if you've got four nodes of a database management system, one of them would have to lock on a row in a table or whatever, it's going to have to propagate that information to the other three nodes on the mainframe side. It would just put it into what we call a coupling facility, and the other Db2 members or instances in the same cluster would be able to check that and see that, no, we can't update that yet, we'll have to wait.
There are lots of different things we use it for. We use it for data replication, which means that we've got an always-on alternate Sysplex cluster several thousand miles away that is propagating the data to that Db2 over there using replication services at the software level rather than, if you physically replicate data and the Db2 or the Oracle environment, physically using storage replication, you've in effect got a cloned copy of that environment. It's going to fire up at the remote site, looking for the network that's at the local site. There are lots of things you would have to do there to do that. Plus the RTO time to actually get that alternate Db2 at the DR side could be 40-45 minutes depending. Whereas we can do this capability and we call it always on, where the RTO is about a minute.
Senior Systems Architect/Analyst/Developer at a logistics company with 1,001-5,000 employees
It's great as a backend database system utilized to store the data for the entire corporate structure.
Due to the fact that we're going to go with the hardware-specifics of the fact that it's bundled in IBM i, it's exceedingly reliable, as the architecture of the IBM i just does not go down.
It runs very well. It runs very solid. It does everything that I expect it to do. It offers all of the standard RDBMS functionalities and capabilities. I consider Db2 to be a direct competitor with Oracle and SQL servers any day of the week. The difference is what flavor of Db2 you're going to run. You're going to run the Linux Unix, are going to run the IBM i version, and then it comes down to, for me, the IBM i, due to the fact that the architecture does not fail. It does not go down. It does not get hacked. There's never been a successful hacking of an IBM i architecture. You're looking at an environment where your data is extremely secure, compared to a lot of the other RDBMS systems.
The solution is configurable and has what you would consider to be a desktop management configuration capability too. You can partition it off, and you can set up different instances of it and such. The interface is more than adequate. There's nothing great about it, there's nothing poor about it. It's more than capable of doing what you need to do if you do need to do DBA maintenance kind of work to it.View full review »
One of the things I like most about Db2 is that it is almost maintenance-free. I do not have to maintain it, unlike a modal database. I have been using modal databases for a long time and those are more sensitive. It is almost 15 years now that I have been using modal databases and it is almost tedious to use modal databases by comparison. I have been using the Db2 more recently and both database types are in use in my company. With a modal database, I have to check to see how or if the data is coming through. But in Db2, it is not as much of a headache. It is also easier to understand than modal database structures.View full review »
It has a good feature called pureScale, which is just for scalability. It is a perfect solution for environments where scalability is going to be an issue.View full review »
Global Infrastructure service manager at a manufacturing company with 10,001+ employees
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.View full review »
It's the best solution in terms of security, performance, and availability because the system is available 24/7.View full review »
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.View full review »
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.
Domain architect at a financial services firm with 10,001+ employees
The solution is a very stable relational database and has integration with legacy systems. It is a great product.View full review »
CEO at a tech services company with 51-200 employees
The solution has very good data compression of up to 50%. For example, if you have 50 terabytes of data, it can be reduced to 25 terabytes.View full review »
The most valuable feature of the IBM Db2 Database is security.View full review »
It's very secure.View full review »
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.View full review »
Software architect at Bergen
The most valuable features are the simplicity of the database and the access to Db2 and Db2 information.View full review »
IT Developer at a financial services firm with 10,001+ employees
IBM Db2 Database has good performance.View full review »
Senior Manager of MIS at Fountain Set
The most valuable feature is PowerPC support.View full review »