BigQuery vs Oracle Big Data Appliance comparison

"It's pretty stable. It's fast, and it is able to go through large quantities of data pretty quickly."

"BigQuery excels at data analysis. It processes vast amounts of information using its advanced architecture and sophisticated querying capabilities, making it crucial for critical insights and safe for handling sensitive data."

"It's similar to a Hadoop cluster, except it's managed by Google."

"The product's most valuable features include its scalability and the ability to handle complex queries on large datasets."

"The solution's reporting, dashboard, and out-of-the-box capabilities match exactly our requirements."

"BigQuery processes a substantial amount of data, whether in gigabytes or terabytes, swiftly producing desired data within one or two minutes."

"The setup is simple."

"The product is serverless. We only need to write SQL queries to analyze the data. We need to pay based on the number of queries. The retrieval time is very less. Even if you write large queries, the tool is able to bring back data in a few seconds."

"Because Big Data Appliance allows me to have a single source of truth, it means I have clean data that can be monetized and leveraged to gain more insights with real-time reports from the dashboard."

"The best thing about the product is that the end-user can build the reports by themselves without really knowing anything about databases."

"The best feature of Oracle Big Data Appliance, from a price perspective for the storage, is because they have technology called the ZFS technology; it offers huge storage with a decent price."

"This is a comprehensive solution that is easy to deploy."

"We'd like to see more local data residency."

"When I execute a query, the dashboard doesn't always present the output seamlessly."

"It would be better if BigQuery didn't have huge restrictions. For example, when we migrate from on-premises to on-premise, the data which handles all ebook characters can be handled on-premise. But in BigQuery, we have huge restrictions. If we have some symbols, like a hash or other special characters, it won't accept them. Not in all cases, but it won't accept a few special characters, and when we migrate, we get errors. We need to use Regexp or something similar to replace that with another character. This isn't expected from a high-range technology like BigQuery. It has to adapt all products. For instance, if we have a TV Showroom, the TV symbol will be there in the shop name. Teradata and Apache Spark accept this, but BigQuery won't. This is the primary concern that we had. In the next release, it would be better if the query on the external table also had cache. Right now, we are using a GCS bucket, and in the native table, we have cache. For example, if we query the same table, it won't cost because it will try to fetch the records from the cached result. But when we run queries on the external table a number of times, it won't be cached. That's a major drawback of BigQuery. Only the native table has the cache option, and the external table doesn't. If there is an option to have an external table for cache purposes, it'll be a significant advantage for our organization."

"It can be slower and more problematic compared to other platforms such as Snowflake."

"So our challenge in Yemen is convincing many people to go to cloud services."

"The solution should reduce its pricing."

"Some of the queries are complex and difficult to understand."

"The product could benefit from improvements in user-friendliness, particularly in terms of the user interface."

"It seems like the deployment of repositories has become more difficult in later versions of the product rather than easier."

"From a technical perspective, Big Data Appliance could be improved with more innovation in the AI and machine-learning parts instead of relying on Cloudera."

"The product should be simplified for the average user."

"BigQuery pricing can increase quickly. It's a high-priced solution."

"The price could be better. Usually, you need to buy the license for a year. Whenever you want more, you can subscribe to it, and you can use it. Otherwise, you can terminate the license. You can use it daily or monthly, and we use it based on a project's requirements."

"The platform is inexpensive."

"The solution is pretty affordable and quite cheap in comparison to PDP or Cloudera."

"Its cost structure operates on a pay-as-you-go model."

"The product’s pricing could be more flexible for end users."

"The pricing is good and there are no additional costs involved."

"The price is a bit high but the technology is worth it."

"Oracle's prices are too high compared to others in the market."