Astra DB is a vector database for developers. In 2025 Datastax, the developer and supporter of Astra DB, was acquired. Astra DB is now available as a component of the IBM watsonx.data Multicloud offering.
N/A
Db2
Score 8.6 out of 10
N/A
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
Oracle Database
Score 8.4 out of 10
N/A
Oracle Database, currently in edition 23ai, is a converged, multimodel database management system. It is designed to simplify development for AI, microservices, graph, document, spatial, and relational applications.
$0.05
per hour
Pricing
Astra DB, now part of IBM watsonx.data
Db2
Oracle Database
Editions & Modules
No answers on this topic
Db2 on Cloud Lite
$0
Db2 on Cloud Standard
$99
per month
Db2 Warehouse on Cloud Flex One
$898
per month
Db2 on Cloud Enterprise
$946
per month
Db2 Warehouse on Cloud Flex for AWS
2,957
per month
Db2 Warehouse on Cloud Flex
$3,451
per month
Db2 Warehouse on Cloud Flex Performance
13,651
per month
Db2 Warehouse on Cloud Flex Performance for AWS
13,651
per month
Db2 Standard Edition
Contact Sales
Db2 Advanced Edition
Contact Sales
Oracle Base Database Service - Standard
$0.0538
per hour
Oracle Base Database Service - Enterprise
$0.1075
per hour
Oracle Base Database Service - High Performance
$0.2218
per hour
Standard Edition
Contact Sales
Enterprise Edition
Contact Sales
Personal Edition
Contact Sales
Offerings
Pricing Offerings
Astra DB, now part of IBM watsonx.data
Db2
Oracle Database
Free Trial
Yes
Yes
Yes
Free/Freemium Version
Yes
Yes
Yes
Premium Consulting/Integration Services
Yes
Yes
No
Entry-level Setup Fee
No setup fee
Optional
No setup fee
Additional Details
—
—
—
More Pricing Information
Community Pulse
Astra DB, now part of IBM watsonx.data
Db2
Oracle Database
Considered Multiple Products
Astra DB, now part of IBM watsonx.data
Verified User
Employee
Chose Astra DB, now part of IBM watsonx.data
We chose Astra as our primary database for time series data was already on Apache Cassandra. We also utilize a small postgres database for relational data within the application, but it made sense to migrate the data to Astra from Apache Cassandra.
Db2 provides a combination of performance and scalability. Security wise, Db2 is always a first choice, especially for the systems where security can't be compromised. For mainframe systems, there is no other DB in the market that can perform better than Db2. If an organization …
From working with other databases, I always felt that Db2 was at the top of its game in all aspects of performance, recoverability, and stability—pretty much everything you want out of an Enterprise database system.
Access controls, encryption, and auditing
capabilities are just a few of the strong security features supported by IBM Db2.I think Strong security features are offered by it, such as integration with Active Directory and LDAP enterprise security infrastructures, row and column …
we have felt Db2 with enhance capability stands better than oracle offering and cost benefit is also there with features like better security and better integration with analytical engines and provision for XML, JSON, text and spatial data formats for different kinds of …
Considering Price, features configurations timelines of the IBM Db2 we found that is very Robust in Scalability, Reliability, Highly Available. also, we are already a IBM products user and we are much satisfied with the overall product as well as customer support from IBM team. …
Db2 is more scalable, reliable, and easily configurable than all the products that we evaluated. We were already using some of the services provided by IBM and were satisfied with the support and pricing. This led us to select Db2 as our database management system.
Compared to similar products, Db2 shared common Relational DataBase Management System (RDBMS) features such as SQL support, data integrity, Atomicity, Consistency, Isolation and Durability (ACID) Compliance and concurrency control. However, the Db2 is designed for scalability, …
Db2 is one of the oldest and mature rdbms available in the market. IBM products were already been used in the organization. Cost effective in terms of licensing.
DB2 works as good as any of these databases. It is cheaper to run than any of them. It is more solid and stable that SQL server or Netezza. It is very comparable to Oracle for reliabilty.
But for administration, Netezza is a little simpler because it has no indexes. Netezza is …
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 …
Db2 is one of the best relational databases I’ve used. It has the ability to maintain large amount of data and execution of million transactions in fraction of a second. If you use it properly, an organization can build a database with thousands of tables, and it can provide …
It's almost not comparable because they all do the same job in varying degrees. There are some things I like about Db2 that I don't enjoy about Oracle, but it mostly comes down to how it works and where it stores everything like SYS tables in Db2. MySQL is probably the fastest …
I did not choose DB2 over any other database engine, the corporation we are currently working for uses all of them for different companies/systems/departments and we need to consolidate data from all of them into a single data warehouse. DB2 is one of the many different data …
I have heard from other similar institutions that they have problems unique to their DB2 database when using the ERP that we have in common. I found the DB2 database system difficult to interact with when I had to use it for a project many years ago. I personally developed some …
The reason why my team and organization chose to go with Oracle Database 12c with it stacked up against IBM's DB2, or Microsoft's SQL server, as when using other Oracle products, it has been much easier in the past to work along side with other Oracle products, which by the way …
MySQL: I used MySQL as part of an old CRM. I think that's also light. But, Oracle seems to have better speed and reliability. DB2: I used DB2 mainly on mainframe and z/OS. I always felt that it's cumbersome to access and write queries on DB2.
Oracle 12c is superior to SQL Server for large mission critical databases and applications.
We also used DB2 in the past. We migrated many of our SAP applications from DB2 to Oracle 11.2 several years ago. These applications are now on Oracle 12c.
We use IBM DB2 in AS400 to handle part of our accounting system and our legacy ERP. We are migrating all functionalities to Oracle Database 12c because it is more secure and stable. We have some applications using SQL Server but we want to handle those systems in it because at …
IBM DB2 is extremely heavy as compared to Oracle and is expensive for the price we pay for the product. MySQL doesn’t have most of the features that Oracle has.
Oracle is placed in a good spot against its competitors. It has advantages over its competitors in its legacy stability and high availability. A common engine to handle relational, JSON, Vector, and graph data makes it more cost-effective. Given all the good features, the …
I have selected Oracle database from other databases as this database is relational database which stored the data in structural and tabular format which is better than any other databases which I have used in my carrier. Also MongoDB is no SQL database where we can use SQL …
Oracle Database is best in business, consistent, and robust. Even the standard version is sufficient for the best performance. The main thing is I have never seen corruption and in my opinion, it is best when used with Linux.
While I was not available for the original selection, the reason I have fought to keep it in place and not change is mainly due to performance and security. The company has sought other options, however, I continue to maintain that this is the best course of action in our …
Oracle Database 12c is far superior to Microsoft SQL Server (or any other database in fact). For starters, Oracle 12c offers much better performance and higher reliability. That itself should make the difference. Oracle 12c is also superior in terms of features. On a high level, …
Microsoft SQL Server is our most commonly used DBMS because most vendors support it. The user interface for SQL Server Management studio is also very easy to use. For this reason, we usually prefer SQL Server over Oracle. However, we also support Oracle because it is a …
While there are several very good relational databases, some are offered by companies where the database is not the key focus. Even though Oracle's software portfolio has expanded greatly over the years, they remain keenly focused on database technology.
We generally choose Oracle 12c whenever the requirements include reliability, scalability, and interconnectivity with existing applications. Most application upgrades are re-hosted in Oracle, if on Oracle. If the application supplier prefers, or has exclusive experience with a …
We've been super happy with Astra DB. It's been extremely well-suited for our vector search needs as described in previous responses. With Astra DB’s high-performance vector search, Maester’s AI dynamically optimizes responses in real-time, adapting to new user interactions without requiring costly retraining cycles.
I have primarily used it as the basis for a SIS - but I have migrated more than a few systems from there database systems to DB2 (Filemaker, MySQL, etc.). DB2 does have a better structural approach, as opposed to Filemaker, which allows for more data consistency, but this can also lead to an inflexibility that can sometimes be counterintuitive when attempting to compensate for the flexibility of the work environment as Schools tend to have an all in one approach.
We migrated from NoSQL to an Oracle database. One of the reasons was robust backup and recovery options available in the Oracle database, which provide zero data loss. A transactional database like Oracle is a better fit for our use case than NoSQL. On a large scale, deployment was evaluated as a cheaper option than the NoSQL engine. This conclusion came even after considering Oracle license is expensive.
We need to be able to process a lot of data (our biggest clients process hundreds of milions of transactions every month). However, it is not only the amount of data, it is also an unpredictable patterns with spikes occuring at different points of time - something athat Astra is great at.
Our processing needs to be extremaly fast. Some of our clients use our enrichment in a synchronous way, meaning that any delay in processing is holding up the whole transaction lifecycle and can have a major impact on the client. Astra is very fast.
A close collaboration with GCP makes our life very easy. All of our technology sits in Google Cloud, so having Astra in there makes it a no-brainer solution for us.
The support team sometimes requires the escalate button pressed on tickets, to get timely responses. I will say, once the ticket is escalated, action is taken.
They require better documentation on the migration of data. The three primary methods for migrating large data volumes are bulk, Cassandra Data Migrator, and ZDM (Zero Downtime Migration Utility). Over time I have become very familiar will all three of these methods; however, through working with the Services team and the support team, it seemed like we were breaking new ground. I feel if the utilities were better documented and included some examples and/or use cases from large data migrations; this process would have been easier. One lesson learned is you likely need to migrate your application servers to the same cloud provider you host Astra on; otherwise, the latency is too large for latency-sensitive applications.
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.
There is a lot of sunk cost in a product like Oracle 12c. It is doing a great job, it would not provide us much benefit to switch to another product even if it did the same thing due to the work involved in making such a switch. It would not be cost effective.
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.
Many of the powerful options can be auto-configured but there are still many things to take into account at the moment of installing and configuring an Oracle Database, compared with SQL Server or other databases. At the same time, that extra complexity allows for detailed configuration and guarantees performance, scalability, availability and security.
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.
Their response time is fast, in case you do not contact them during business hours, they give a very good follow-up to your case. They also facilitate video calls if necessary for debugging.
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.
1. I have very good experience with Oracle Database support team. Oracle support team has pool of talented Oracle Analyst resources in different regions. To name a few regions - EMEA, Asia, USA(EST, MST, PST), Australia. Their support staffs are very supportive, well trained, and customer focused. Whenever I open Oracle Sev1 SR(service request), I always get prompt update on my case timely. 2. Oracle has zoom call and chat session option linked to Oracle SR. Whenever you are in Oracle portal - you can chat with the Oracle Analyst who is working on your case. You can request for Oracle zoom call thru which you can share the your problem server screen in no time. This is very nice as it saves lot of time and energy in case you have to follow up with oracle support for your case. 3.Oracle has excellent knowledge base in which all the customer databases critical problems and their solutions are well documented. It is very easy to follow without consulting to support team at first.
Overall the implementation went very well and after that everything came out as expected - in terms of performance and scalability. People should always install and upgrade a stable version for production with the latest patch set updates, test properly as much as possible, and should have a backup plan if anything unexpected happens
Graph, search, analytics, administration, developer tooling, and monitoring are all incorporated into a single platform by Astra DB. Mongo Db is a self-managed infrastructure. Astra DB has Wide column store and Mongo DB has Document store. The best thing is that Astra DB operates on Java while Mongo DB operates on C++
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.
Because of a rich user base and support for any critical issue, this is one of the best options to choose. In case the project has a TCO issue, it can compromise and choose Postgres as the best alternative. SQL server is also good and easy to code and maintain but performance is not as good as the Oracle
We are well aware of the Cassandra architecture and familiar with the open source tooling that Datastax provides the industry (K8sSandra / Stargate) to scale Cassandra on Kubernetes.
Having prior knowledge of Cassandra / Kubernetes means we know that under the hood Astra is built on infinitely scalable technologies. We trust that the foundations that Astra is built on will scale so we know Astra will scale.
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!!