DB2 is a family of relational database software solutions offered by IBM. It includes standard Db2 and Db2 Warehouse editions, either deployable on-cloud, or on-premise.
$0
MariaDB Platform
Score 7.7 out of 10
N/A
MariaDB is an open-source relational database made by the original developers of MySQL, supported by the MariaDB Foundation and a community of developers. The community states recent additional capabilities as including clustering with Galera Cluster 4, compatibility with Oracle Database, and Temporal Data Tables, allowing one to query the data as it stood at any point in the past.
I could think of a couple but the obvious is in Fintech and Retail, because of the amount of transactional and event level data for global operations. It is imperative to have a solution that can handle such large scale date, in real-time and batch delivery for inbound and outbound delivery, and ultimately ensuring that workload management is supported in some cases for around the clock SLAs.
DB2 maintains itself very well. The Task Scheduler component of DB2 allows for statistics gathering and reorganization of indexes and tables without user interaction or without specific knowledge of cron or Windows Task Scheduler / Scheduled jobs.
Its use of ASYNC, NEARSYNC, and SYNC HADR (High Availability Disaster Recovery ) models gives you a range of options for maintaining a very high uptime ratio. Failover from PRIMARY to SECONDARY becomes very easy with just a single command or windowed mouse click.
Task Scheduler ( DB2 9.7 and earlier ) allows for jobs to be run within other jobs, and exit and error codes can define what other jobs are run. This allows for ease of maintenance without third party softwares.
Tablespace usage and automatic storage help keep your data segmented while at rest, making partitioning easier.
Ability to run commands via CLI (Command Line Interface) or via Control Center / Data Studio ( DB2 10.x+) makes administration a breeze.
Simpler learning curve. MariaDB is a cleaner, simpler system that is (IMO) easier to learn and easier to manage effectively than many other database systems.
Lower hardware requirements. After migrating to MariaDB from another database software system, we find that our hardware needs have substantially decreased.
MariaDB support is very responsive. It's like they actually care. On the few occasions we've run into technical issues, support has always come through with what we needed. Once it was showing me a relatively new feature the server supported that I wasn't aware of, that, once I was able to properly make use of it helped me resolve a serious production performance issue.
Architectural flexibility. As an example, the ready availability of synchronous (Galera) versus asynchronous replication schemes without being locked into one of the other by enormous technical complexity or punitive licensing, allows the customer to find what really works best for their needs.
Driver Support - Some third party applications use database drivers that cause unexplained slowness with MariaDB. This can be worked around by using the MySQL drivers, but it's not clear what causes the problem in the first place.
Support - While online communities are helpful in diagnosing problems, there isn't as much professional documentation/support available for MariaDB as some of the other major database options.
Data Visualization - It would be helpful if there were more built in options for analyzing statistics and generating reports.
The DB2 database is a solid option for our school. We have been on this journey now for 3-4 years so we are still adapting to what it can do. We will renew our use of DB2 because we don’t see. Major need to change. Also, changing a main database in a school environment is a major project, so we’ll avoid that if possible.
You have to be well versed in using the technology, not only from a GUI interface but from a command line interface to successfully use this software to its fullest.
MariaDB is very usable and stable to be used in production settings as an alternative to MySQL. The shortcomings of SQL are present but well understood in the community, and if the decision were to be made again, I would choose MariaDB over MySQL on future projects.
I have never had DB2 go down unexpectedly. It just works solidly every day. When I look at the logs, sometimes DB2 has figured out there was a need to build an index. Instead of waiting for me to do it, the database automatically created the index for me. At my current company, we have had zero issues for the past 8 years. We have upgrade the server 3 times and upgraded the OS each time and the only thing we saw was that DB2 got better and faster. It is simply amazing.
The performances are exceptional if you take care to maintain the database. It is a very powerful tool and at the same time very easy to use. In our installation, we expect a DB machine on the mainframe with access to the database through ODBC connectors directly from branch servers, with fabulous end users experience.
Easily the best product support team. :) Whenever we have questions, they have answered those in a timely manner and we like how they go above and beyond to help.
We have launched several inquiries to MariaDB support and they have always responded very quickly and have not been tutoring for the duration of the incident/problem.
Likewise, they want to hold constant meetings with the client to get their opinion as well as how they can help.
I see a very human support and concerned about the customer.
DB2 was more scalable and easily configurable than other products we evaluated and short listed in terms of functionality and pricing. IBM also had a good demo on premise and provided us a sandbox experience to test out and play with the product and DB2 at that time came out better than other similar products.
MariaDB stacks up the the competition just fine. Due to is ture open source nature we do not have to worry about licencing and spending money on nothing. Moreover, MariaDB does everything that we need to get done. We can run data that is a million rows or many smaller projects on the same environment with little overhead. One of the best features that MariaDB has is the ability of backup or dump data to standard text sql statements. That was one of the reasons why we choose MariaDb because it makes backups or transferring data a snap
By using DB2 only to support my IzPCA activities, my knowledge here is somewhat limited.
Anyway, from what I was able to understand, DB2 is extremely scallable.
Maybe the information below could serve as an example of scalability.
Customer have an huge mainframe environment, 13x z15 CECs, around 80 LPARs, and maybe more than 50 Sysplexes (I am not totally sure about this last figure...)
Today we have 7 IzPCA databases, each one in a distinct Syplex.
Plans are underway to have, at the end, an small LPAR, with only one DB2 sub-system, and with only one database, then transmit the data from a lot of other LPARs, and then process all the data in this only one database.
The IzPCA collect process (read the data received, manipulate it, and insert rows in the tables) today is a huge process, demanding many elapsed hours, and lots of CPU.
Almost 100% of the tables are PBR type, insert jobs run in parallel, but in 4 of the 7 database, it is a really a huge and long process.
Combining the INSERTs loads from the 7 databases in only one will be impossible.......,,,,
But, IzPCA recently introduced a new feature, called "Continuous Collector".
By using that feature, small amounts of data will be transmited to the central LPAR at every 5 minutes (or even less), processed immediately,in a short period of time, and withsmall use of CPU, instead of one or two transmissions by day, of very large amounts of data and the corresponding collect jobs occurring only once or twice a day, with long elapsed times, and huge comsumption of CPU
I suspect the total CPU seconds consumed will be more or less the same in both cases, but in the new method it will occur insmall bursts many times a day!!
Fast response time by processing optimization and cost reduction by reduced CPU utilization. Nowadays, good performance is a necessary condition for the survival of a company and its sustained growth
SQL enhancements are targeted to improve performance, simplify current and new applications, and reduce the development cycle time to market.
A CPU reduction at peak times can immediately reduce our TCO by reducing software costs related to CPU utilization.
Impressive reductions in memory requirements, which used to limit the concurrent database activity
Out-of-the-box savings without changing the database or application
