Last week in the BigQuery reference guide, we walked through query execution and how to leverage the query plan. This week, we’re going a bit deeper - covering more advanced queries and tactical optimization techniques. Here, we’ll walk through some query concepts and describe techniques for optimizing related SQL.
In our previous blog, we talked about the four paths to Cloudera Data Platform. If you haven’t read that yet, we invite you to take a moment and run through the scenarios in that blog. The four strategies will be relevant throughout the rest of this discussion. Today, we’ll discuss an example of how you might make this decision for a cluster using a “round of elimination” process based on our decision workflow.
“40% of all enterprise workloads will be deployed in CIPS [cloud infrastructure and platform services] by 2023, up from only 20% in 2020.”.As the cloud permeates every aspect of business, decision-makers must make critical choices regarding infrastructure at every turn. Their answers will ultimately determine if every part of an organization is empowered to move forward in a cohesive way to reach business outcomes.
Customers wanting to drive self-service analytics as part of creating a data-driven organization will often ask, “Can we achieve self service analytics, when our work force has low data literacy?” Or they might say they are not ready for self-service analytics, incorrectly thinking they need first to improve data literacy. But the two are inextricably linked. I liken it to teaching a child to read without giving them any books on which to build their skills.
Historically, maintenance has been driven by a preventative schedule. Today, preventative maintenance, where actions are performed regardless of actual condition, is giving way to Predictive, or Condition-Based, maintenance, where actions are based on actual, real-time insights into operating conditions. While both are far superior to traditional Corrective maintenance (action only after a piece of equipment fails), Predictive is by far the most effective.
In traditional data warehouses, specific types of data are stored using a predefined database structure. Due to this “schema on write” approach, prior to all data sources being consolidated into one warehouse, there needs to be a significant transformation effort. From there, data lakes emerge!
Over the past two decades, marketers have faced an uphill battle in trying to turn marketing into a fully data-driven discipline. Our challenge is not that we don’t have enough data but that data has been difficult to access and use. Marketing, sales, and product data is scattered across different systems, and we can’t get a complete picture of what is going on in our businesses.
