Overview
ProductRatingMost Used ByProduct SummaryStarting Price
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
Google BigQuery
Score 8.7 out of 10
N/A
Google's BigQuery is part of the Google Cloud Platform, a database-as-a-service (DBaaS) supporting the querying and rapid analysis of enterprise data.
$0.04
PostgreSQL
Score 8.7 out of 10
N/A
PostgreSQL (alternately Postgres) is a free and open source object-relational database system boasting over 30 years of active development, reliability, feature robustness, and performance. It supports SQL and is designed to support various workloads flexibly.N/A
Pricing
Db2Google BigQueryPostgreSQL
Editions & Modules
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
Standard edition
$0.04 / slot hour
Enterprise edition
$0.06 / slot hour
Enterprise Plus edition
$0.10 / slot hour
No answers on this topic
Offerings
Pricing Offerings
Db2Google BigQueryPostgreSQL
Free Trial
YesYesNo
Free/Freemium Version
YesYesNo
Premium Consulting/Integration Services
NoNoNo
Entry-level Setup FeeOptionalNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
Db2Google BigQueryPostgreSQL
Considered Multiple Products
Db2
Chose Db2
We are underway to evaluate both, in their benefits versus concerns. One thing that makes IBM Db2 better is it is a very mature database with great performance
Chose Db2
The decision to select IBM Db2 is typically driven by specific enterprise needs:Mission-Critical Workloads: Db2 is built to handle highly demanding transactional (OLTP) and analytical (OLAP) workloads with high reliability and continuous availability via features like Db2 …
Chose Db2
Works well for Active Active environments
Chose Db2
Db2 for i SQL is much more standard compliant than SQL Servers dialect. And with Visual Explain its much easier to optimize SQL queries for optimal performance.
Chose Db2
IBM watsonx.data, PostgreSQL and MongoDB
Chose Db2
We chose Db2 for our organization because, in our experience it is Less in cost when bundled with IBM products and for the Ease of use and maintenance
Chose Db2
other are costly and have to have multiple things to be able to use their licenses are needed
Chose Db2
Oracle Database and Microsoft SQL Server
Chose Db2
Budget availability for making sure product stands test of time for scalability, secure and able to handle large data sets
Chose Db2
Although each are good, DB2 provides greater scalability, flexibility for data integrity.
Chose Db2
I have used DBArtisan before in another project with similar use cases, and both are very reliable and work well. As this application is compatible with their platforms, the current company is using the IBM db2 for the work.
Chose Db2
DB2 was selected for handling financial data due to its solidity.
Chose Db2
Oracle and Microsoft are the ones that we have more to compare with and they are on par with Db2. Postgres is the small solution that usually we leave behind and move to Db2.
Mongo is the one that is different from what I used Db2 for but I know it has the capability to use …
Google BigQuery
Chose Google BigQuery
Fully serverless. We don’t manage clusters or warehouses. Requires us to manage virtual warehouses. BigQuery is cheaper for exploratory heavy queries; Snowflake is more predictable for sustained workloads. BigQuery is unbeatable if you’re deep in Google’s ecosystem; Snowflake …
Chose Google BigQuery
Google BigQuery of course collects a much much larger array of raw data and can handle (practically) an unlimited amount of data. For a large enterprise like ours that relies on large-scale analytics, this is absolutely imperative. Google BigQuery can also combine GA4 data with …
Chose Google BigQuery
Compared to PostgreSQL and MySQL, Google BigQuery is faster and more scalable for large datasets. It’s serverless, so there’s no need to manage infrastructure. We chose Google BigQuery for its ease of use built-in analytics features
Chose Google BigQuery
The architecture of ETL was influenced by Data processing component which is Dataproc and there was a need for easy Query console with Access control capabilities with lesser overhead in managing the permission. This made the decision to move with Google BigQuery compare to …
Chose Google BigQuery
is much better as it’s easily accessible provides velvet documentation and fulfils all our needs as well as easily integrated into clients, environment
Chose Google BigQuery
Google BigQuery is simpler and I say it has simpler UI too.
If you have a clear long term ask , mainly business intelligence needs then Google BigQuery offers you good.
If you need too much of features under a single cloud and you are ok to be lil clumsy then you can check …
Chose Google BigQuery
I have used most of the data analytics platforms. Based on my work, I have found that the user interface of Google BigQuery is simple to navigate. I like the front view - ease of joining tables, and integration with other platforms.
Chose Google BigQuery
Compared to every other analytics DB solution I've used, Google BigQuery was by far the easiest to set up and maintain, and scale.
The price was also much lower for our use case (internal data analysis).
Chose Google BigQuery
For our usage, Google BigQuery is cheaper and more performant. The others have their place, but in certain scenarios, Google BigQuery is a better solution.
Chose Google BigQuery
We actually use Snowflake and BigQuery in tandem because they both currently meet various needs. Redshift, however, has barely been used since our migration away from it. In the case of both Snowflake and BigQuery, they beat Redshift by a long shot. The main reasons are their …
Chose Google BigQuery
PowerBI can connect to GA4 for example but the data processing is more complicated and it takes longer to create dashboards. Azure is great once the data import has been configured but it's not an easy task for small businesses as it is with BigQuery.
Chose Google BigQuery
I came to use BigQuery from a traditional system like MS SQL server, the features which are available in BigQuery as a cloud service far outweigh the features from SQL server. I have not used other similar tools like Amazon Redshift but Google BigQuery serves multiple use cases …
Chose Google BigQuery
Google BigQuery is cheaper and much faster as compared to both. While as compared to Snowflake , we tested it was faster and cheaper by 30%, that is after Snowflake tweaked their environment, if not for that it would have been 90% cheaper than snowflake. Redshift is not easy …
Chose Google BigQuery
In my opinion, Google BigQuery is custom made to be the best data lake system that is easy to use, scalas to fit any business size, has inbuilt security, as well as tools for data integrity. Although a few other tools have some of the same functionality, Google BigQuery is the …
Chose Google BigQuery
It's easier to connect data between BigQuery and looker studio instead of connecting the data between BigQuery and tableau in terms of data explore or dashboard creating. Therefore we are considering migrating dashboards from tableau to looker studio for the whole company.
On …
Chose Google BigQuery
When comparing Google BigQuery and Databricks, both platforms are powerful tools for managing and analyzing large datasets. BQ is ideal for businesses requiring large-scale analytics, reporting, and dashboarding with minimal operational overhead. It’s also great for ad-hoc …
Chose Google BigQuery
Google BigQuery's main advantage over its direct competitors (Amazon Redshift and Azure Synapse) is that it is widely supported by non-Google software, while the others rely heavily on their own cloud ecosystems.
Chose Google BigQuery
I have used other data manipulation tools like SQL Server and Google BigQuery feels more intuitive, Google provides so much documentation and tutorials that getting to know the software is not only easy but even satisfactory, so I'd say Google BigQuery is very superior to that …
Chose Google BigQuery
Main reason is how it integrates directly with the google ecosystem which really facilitates the automatization proceses for the whole company. This ensures that sales and all the other departments have the correct information on a daily bases with a ease of use with day to day …
Chose Google BigQuery
Amazon Redshift was a likely alternative we were considering , but it needs to be provisioned on cluster and nodes, which increases infrastructure management, whereas Google BigQuery is serverless, so no infra management :) Also, I remember when comparing them we did found out …
Chose Google BigQuery
Its same as compared to Big query. We go with big query because of clients requirements in project.
Chose Google BigQuery
Google BigQuery as a platform allows for more integrations and customizability than many other offerings. Users mostly need to understand the basics of database and SQL programming in order to get the most from the product. However, other products like Hevo do have less of a …
PostgreSQL
Chose PostgreSQL
My expirence with other solutions is very limited, but what I saw/heard is, that on Azure the managed MS SQL Server is said to be more flexible and you can use it in a serverless-ish fashion. But on the other hand, PostgresSQL is still strong regarding its efficiency. And in my …
Chose PostgreSQL
Being open source, PostgreSQL offers the highest performance among its peers. It has a strong support community where we can find solutions to most of the queries. It's suited for GIS (Geospatial) based applications, making it unique from its peers. There are fewer databases …
Chose PostgreSQL
We had to use PostgreSQL as that is the DB preferred by our SaaS Provider.
Chose PostgreSQL
PostgreSQL holds it own against both these options. Some of these DBs are in play for certain needs but the majority are PostgreSQL because of cost and operational performance.
Chose PostgreSQL
In my experience using all of these products over many years, PostgreSQL is better than any of them in reliability, performance, productivity, cost, scalability and interoperability across operating systems.
Chose PostgreSQL
MySQL is an Oracle product which has in itself some known issues due to that (support, contract terms). Based on my knowledge, PostgreSQL support everything that MySQL support (syntax wise) and it adds more improvements and syntaxes that make the life of database engineers and …
Chose PostgreSQL
First It's open source and it's cost-effective compared to other databases.PostgreSQL can be easily integrated with numerous platforms. It is well known and appreciated so relying on it as our system database can be easily accepted by our customers. And if your developing a …
Chose PostgreSQL
For our use cases, PostgreSQL is just as feature rich as other options, costs less, and is simple to get up and running. There is also a plethora of documentation to support it which makes it a great option for a small scale startup without needing high levels of expertise to …
Chose PostgreSQL
In this case, Postgres is preferred because it handles large data sets and requires fewer hardware resources than its competitor, MySQL. Compared to PostgreSQL, Microsoft products are excellent, but the installation process for MS SQL is lengthy. PostgreSQL has an advantage …
Chose PostgreSQL
I've been using different databases for the past 20 years, solutions like MS SQL Server, MySQL, MariaDB, Interbase, Firebird, DB2, etc., and by using them I wasn't able to be neither close to the performance PostgreSQL deliver. Also, it is one of the most popular databases on …
Chose PostgreSQL
Although the competition between the different databases is increasingly aggressive in the sense that they provide many improvements, new functionalities, compatibility with complementary components or environments, in some cases it requires that it be followed within the same …
Chose PostgreSQL
We evaluated both PostgreSQL and MySQL, two popular open source relational databases. While they are very similar in most areas, PostgreSQL's reliability and performance won us over, plus it has much better support from cloud vendors we also work with.
Chose PostgreSQL
Postgres stacks up just [fine] along the other big players in the RDBMS world. It's very popular for a reason. It's very close to mySQL in terms of cost and features - I'd pick either solution and be just as happy. Compared to Oracle it is a MUCH cheaper solution that is just …
Chose PostgreSQL
A free corporate professional product. Who does not want to have such a thing, we hesitated because we did not know the product before and frankly we did not want it at first. But when we give it a chance, it has been running smoothly for years.
Chose PostgreSQL
When we were originally evaluating Redshift we ran into some issue with dates. Either way, Postgres is a better choice than Redshift because it avoids vendor lockin. We ended up choosing Postgres over MySQL because it was easier at the time to get a hosted Postgres cluster up …
Chose PostgreSQL
As I have been telling all along, PostgreSQL is much cheaper compared to the other RDBMS solutions. It has got better performance with some of the application services that we are using and is easy to maintain. Overall, we are satisfied migrating to PostgreSQL database clusters.
Chose PostgreSQL
Much more mature and stable when compared to MySQL with features such as MVCC, complex subquery plans, ORDBMS, and NoSQL support. With Oracle retaining rights to MySQL its future as an open database is less secure and is no longer in the hands of the community. PostgreSQL also …
Chose PostgreSQL
Its main characteristic is the integrity of the data. In addition, being free software, it has no costs associated with its license, which allows the number of installations to be scaled without problems.
The technical staff quickly learns about its installation, configuration …
Chose PostgreSQL
Both Oracle and MS-SQL database option fell when we evaluated the effect on our overall solution cost to our customers. customer examine the overall cost of the solution they buy, selecting Oracle or MS-SQL would leave less money in our pockets.
We are Linux based solutions and …
Chose PostgreSQL
PostgrPostgreSQL as a transaction db engine against oracle and sql server works well. TPM wise compared to MySQL and MariaDB, on an evan scale.
SQL function supports, far outweighs compared to MySQL and MariaDB. PG Extensions allow for flexibiltity and scalability. Allows …
Chose PostgreSQL
We selected PostgreSQL due to the number of employees who have used it in the past.
The data consistency guarantees.
The multiple transaction isolation levels support.
Chose PostgreSQL
PostgreSQL outperforms every other option. It is faster, more flexible, more reliable, easier to maintain, and more consistent in behaviour than any of the other offerings.
Chose PostgreSQL
The main reason for select PostgreSQL against MS SQL Server Express edition is the necessity to use open-source platform, without any issues for licensing, client licensing, etc. etc, which is usually follows developers and project managers when they start to use products and …
Chose PostgreSQL
I think Postgres stacks up great against all modern database solutions and has continued to be a trend leader in this space.
Features
Db2Google BigQueryPostgreSQL
Database-as-a-Service
Comparison of Database-as-a-Service features of Product A and Product B
Db2
-
Ratings
Google BigQuery
8.5
Ratings
0% above category average
PostgreSQL
-
Ratings
Automatic software patching00 Ratings8.00 Ratings00 Ratings
Database scalability00 Ratings9.00 Ratings00 Ratings
Automated backups00 Ratings8.50 Ratings00 Ratings
Database security provisions00 Ratings8.80 Ratings00 Ratings
Monitoring and metrics00 Ratings8.50 Ratings00 Ratings
Automatic host deployment00 Ratings8.00 Ratings00 Ratings
Best Alternatives
Db2Google BigQueryPostgreSQL
Small Businesses
InterSystems IRIS
InterSystems IRIS
Score 8.1 out of 10
IBM Cloudant
IBM Cloudant
Score 7.4 out of 10
InfluxDB
InfluxDB
Score 9.0 out of 10
Medium-sized Companies
InterSystems IRIS
InterSystems IRIS
Score 8.1 out of 10
IBM Cloudant
IBM Cloudant
Score 7.4 out of 10
SQLite
SQLite
Score 8.0 out of 10
Enterprises
SAP IQ
SAP IQ
Score 6.0 out of 10
IBM Cloudant
IBM Cloudant
Score 7.4 out of 10
SQLite
SQLite
Score 8.0 out of 10
All AlternativesView all alternativesView all alternativesView all alternatives
User Ratings
Db2Google BigQueryPostgreSQL
Likelihood to Recommend
9.0
(0 ratings)
9.0
(0 ratings)
8.3
(0 ratings)
Likelihood to Renew
7.9
(0 ratings)
8.1
(0 ratings)
9.0
(0 ratings)
Usability
8.8
(0 ratings)
6.8
(0 ratings)
8.3
(0 ratings)
Availability
9.2
(0 ratings)
7.3
(0 ratings)
9.0
(0 ratings)
Performance
9.1
(0 ratings)
6.4
(0 ratings)
7.0
(0 ratings)
Support Rating
8.9
(0 ratings)
5.0
(0 ratings)
9.3
(0 ratings)
In-Person Training
8.2
(0 ratings)
-
(0 ratings)
-
(0 ratings)
Implementation Rating
5.6
(0 ratings)
-
(0 ratings)
9.0
(0 ratings)
Configurability
9.1
(0 ratings)
6.4
(0 ratings)
-
(0 ratings)
Ease of integration
7.8
(0 ratings)
7.3
(0 ratings)
-
(0 ratings)
Product Scalability
8.4
(0 ratings)
7.3
(0 ratings)
8.0
(0 ratings)
Vendor post-sale
9.0
(0 ratings)
-
(0 ratings)
-
(0 ratings)
Vendor pre-sale
9.0
(0 ratings)
-
(0 ratings)
-
(0 ratings)
User Testimonials
Db2Google BigQueryPostgreSQL
Likelihood to Recommend
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.
Read full review
Google BigQuery is great for being the central datastore and entry point of data if you're on GCP. It seamlessly integrates with other Google products, meaning you can ingest data from other Google products with ease and little technical knowledge, and all of it is near real-time. Being serverless, BigQuery will scale with you, which means you don't have to worry about contention or spikes in demand/storage. This can, however, mean your costs can run away quickly or mount up at short notice.
Read full review
Based on my experience, PostgreSQL is exactly what I imagine when thinking of a relational database: it is fast for querying and intuitive (if the underlying relations have been well written) and its writes are also efficient. Of course you need to know that a relational database is what you need, for example I would not recommend it if you have a lot of unstructured data that have no way to create a relation from and if you need to run heavy aggregations over your data, as it is not where PostgreSQL would shine.
Read full review
Pros
  • 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.
Read full review
  • Its serverless architecture and underlying Dremel technology are incredibly fast even on complex datasets. I can get answers to my questions almost instantly, without waiting hours for traditional data warehouses to churn through the data.
  • Previously, our data was scattered across various databases and spreadsheets and getting a holistic view was pretty difficult. Google BigQuery acts as a central repository and consolidates everything in one place to join data sets and find hidden patterns.
  • Running reports on our old systems used to take forever. Google BigQuery's crazy fast query speed lets us get insights from massive datasets in seconds.
Read full review
  • The stability it offers, its speed of response and its resource management is excellent even in complex database environments and with low-resource machines.
  • The large amount of resources it has in addition to the many own and third-party tools that are compatible that make productivity greatly increase.
  • The adaptability in various environments, whether distributed or not, [is a] complete set of configuration options which allows to greatly customize the work configuration according to the needs that are required.
  • The excellent handling of referential and transactional integrity, its internal security scheme, the ease with which we can create backups are some of the strengths that can be mentioned.
Read full review
Cons
  • everything about Db2 is 'heavy', even the Community edition and some of the clients
  • difficult to configure for beginners /option overload
  • LUW and z platforms have minor inconsistencies that really should be a non-issue
  • support seems to be declining in terms of quality/quickness of responses
Read full review
  • It is challenging to predict costs due to BigQuery's pay-per-query pricing model. User-friendly cost estimation tools, along with improved budget alerting features, could help users better manage and predict expenses.
  • The BigQuery interface is less intuitive. A more user-friendly interface, enhanced documentation, and built-in tutorial systems could make BigQuery more accessible to a broader audience.
Read full review
  • The query syntax for JSON fields is unwieldy when you start getting into complex queries with many joins.
  • I wish there was a distinction (a flag) you could set for automated scripts vs working in the psql CLI, which would provide an 'Are you sure you want to do X?' type prompt if your query is likely to affect more than a certain number of rows. Especially on updates/deletes. Setting the flag in the headless(scripted) flow would disable the prompt.
  • Better documentation around JSON and Array aggregation, with more examples of how the data is transformed.
Read full review
Likelihood to Renew
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.
Read full review
We have to use this product as its a 3rd party supplier choice to utilise this product for their data side backend so will not be likely we will move away from this product in the future unless the 3rd party supplier decides to change data vendors.
Read full review
As a needed software for day to day development activities
Read full review
Usability
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.
Read full review
web UI is easy and convenient. Many RDBMS clients such as aqua data studio, Dbeaver data grid, and others connect. Range of well-documented APIs available. The range of features keeps expanding, increasing similar features to traditional RDBMS such as Oracle and DB2
Read full review
Postgresql is the best tool out there for relational data so I have to give it a high rating when it comes to analytics, data availability and consistency, so on and so forth. SQL is also a relatively consistent language so when it comes to building new tables and loading data in from the OLTP database, there are enough tools where we can perform ETL on a scalable basis.
Read full review
Reliability and Availability
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.
Read full review
I have never had any significant issues with Google Big Query. It always seems to be up and running properly when I need it. I cannot recall any times where I received any kind of application errors or unplanned outages. If there were any they were resolved quickly by my IT team so I didn't notice them.
Read full review
PostgreSQL's availability is top notch. Apart from connection time-out for an idle user, the database is super reliable.
Read full review
Performance
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.
Read full review
I think Google Big Query's performance is in the acceptable range. Sometimes larger datasets are somewhat sluggish to load but for most of our applications it performs at a reasonable speed. We do have some reports that include a lot of complex calculations and others that run on granular store level data that so sometimes take a bit longer to load which can be frustrating.
Read full review
The data queries are relatively quick for a small to medium sized table. With complex joins, and a wide and deep table however, the performance of the query has room for improvement.
Read full review
Support Rating
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.
Read full review
BigQuery can be difficult to support because it is so solid as a product. Many of the issues you will see are related to your own data sets, however you may see issues importing data and managing jobs. If this occurs, it can be a challenge to get to speak to the correct person who can help you.
Read full review
There are several companies that you can contract for technical support, like EnterpriseDB or Percona, both first level in expertise and commitment to the software.
But we do not have contracts with them, we have done all the way from googling to forums, and never have a problem that we cannot resolve or pass around. And for dozens of projects and more than 15 years now.
Read full review
In-Person Training
the material was very clear and all subjects have been handled
Read full review
No answers on this topic
No answers on this topic
Online Training
No answers on this topic
No answers on this topic
The online training is request based. Had there been recorded videos available online for potential users to benefit from, I could have rated it higher. The online documentation however is very helpful. The online documentation PDF is downloadable and allows users to pace their own learning. With examples and code snippets, the documentation is great starting point.
Read full review
Implementation Rating
db2 work well with the application, also the replication tool can keep it up
Read full review
No answers on this topic
The online documentation of the PostgreSQL product is elaborate and takes users step by step.
Read full review
Alternatives Considered
With the other two mentioned above, I needed to have processes and frameworks that executed outside of the environment driving DB management operations. Yes, these are completely different solutions; however, the support you get for framework, library, and language support allows for runtime at a different layer than with other solutions.
Read full review
Google BigQuery of course collects a much much larger array of raw data and can handle (practically) an unlimited amount of data. For a large enterprise like ours that relies on large-scale analytics, this is absolutely imperative. Google BigQuery can also combine GA4 data with external sources (like CRM tools), so our analytics can be unified. Due to our heavy reliance on GA4, Google BigQuery is the natural choice since it is a Google product and has better integration.
Read full review
In my experience using all of these products over many years, PostgreSQL is better than any of them in reliability, performance, productivity, cost, scalability and interoperability across operating systems.
Read full review
Scalability
DB2 can be configured and can work with a variety of applications as opposed to how it was designed initially to only with with IBM mainframes. It's easy implementation process makes it a good buy for many organizations to scale their applications to be the best in terms of versatility, resilience and application performance
Read full review
We have continued to expand out use of Google Big Query over the years. I'd say its flexibility and scalability is actually quite good. It also integrates well with other tools like Tableau and Power BI. It has served the needs of multiple data sources across multiple departments within my company.
Read full review
The DB is reliable, scalable, easy to use and resolves most DB needs
Read full review
Return on Investment
  • Time efficiency is the major point to highlight, especially the minimal time this takes while querying a larger set of data.
  • Reliability becomes another major factor as the application can be accessed at any point in time.
  • Users might initially find it challenging to use the application.
Read full review
  • In some places, Google BigQuery has helped us save some money by avoiding the need for expensive infrastructure and reducing some of the operational costs.
  • Scalability is up-to-date and really helpful in multiple places.
  • Knowledge transfer is easy as it is very user-friendly, so the learning curve has been reduced.
  • Also, it gives us more insights from our data, helping us make smarter decisions for our business.
Read full review
  • A robust and reliable platform reduces the risk of data loss and confusion.
  • Using an almost free product is economical. No license fees = minimal ownership cost.
  • Efficiency is high due to quickness and excellent resource management.
  • PostgreSQL helps us achieve our goals, and there are no time-consuming management tasks.
Read full review
ScreenShots

Db2 Screenshots

Screenshot of Db2 - Data sharingScreenshot of Db2 - Machine LearningScreenshot of Db2 - Real time insights

Google BigQuery Screenshots

Screenshot of Migrating data warehouses to BigQuery - Features a streamlined migration path from Netezza, Oracle, Redshift, Teradata, or Snowflake to BigQuery using the fully managed BigQuery Migration Service.Screenshot of bringing any data into BigQuery - Data files can be uploaded from local sources, Google Drive, or Cloud Storage buckets, using BigQuery Data Transfer Service (DTS), Cloud Data Fusion plugins, by replicating data from relational databases with Datastream for BigQuery, or by leveraging Google's data integration partnerships.Screenshot of generative AI use cases with BigQuery and Gemini models - Data pipelines that blend structured data, unstructured data and generative AI models together can be built to create a new class of analytical applications. BigQuery integrates with Gemini 1.0 Pro using Vertex AI. The Gemini 1.0 Pro model is designed for higher input/output scale and better result quality across a wide range of tasks like text summarization and sentiment analysis. It can be accessed using simple SQL statements or BigQuery’s embedded DataFrame API from right inside the BigQuery console.Screenshot of insights derived from images, documents, and audio files, combined with structured data - Unstructured data represents a large portion of untapped enterprise data. However, it can be challenging to interpret, making it difficult to extract meaningful insights from it. Leveraging the power of BigLake, users can derive insights from images, documents, and audio files using a broad range of AI models including Vertex AI’s vision, document processing, and speech-to-text APIs, open-source TensorFlow Hub models, or custom models.Screenshot of event-driven analysis - Built-in streaming capabilities automatically ingest streaming data and make it immediately available to query. This allows users to make business decisions based on the freshest data. Or Dataflow can be used to enable simplified streaming data pipelines.Screenshot of predicting business outcomes AI/ML - Predictive analytics can be used to streamline operations, boost revenue, and mitigate risk. BigQuery ML democratizes the use of ML by empowering data analysts to build and run models using existing business intelligence tools and spreadsheets.