Finance leaders are facing the most turbulent trading conditions for more than a generation. The odds of recession are rising, US inflation has hit a 40-year peak, the “Great Resignation” has denied organisations the people they urgently need to go to market, stock markets have slumped, exchange rates are beyond volatile and, although abating, there is still the threat of a fresh round of Covid. Forecasting business performance has never been so challenging.

Pub/Sub’s ingestion of data into BigQuery can be critical to making your latest business data immediately available for analysis. Until today, you had to create intermediate Dataflow jobs before your data could be ingested into BigQuery with the proper schema. While Dataflow pipelines (including ones built with Dataflow Templates) get the job done well, sometimes they can be more than what is needed for use cases that simply require raw data with no transformation to be exported to BigQuery.

As Business Intelligence (BI) tools, data warehousing solutions, and enterprise data and application landscapes have advanced, it’s worth taking the time to rethink that old model, starting with the dichotomy between operational reporting (OR) and strategic analytics. There is a clear difference between operational reporting and BI, but they can and should work together. Companies use one or the other, and if they have both, there is a gap between them.

Snowflake’s Data Cloud is powered by a single engine. From day 1, we have been focusing on consistently evolving and improving this engine to allow existing workloads to run more efficiently and enable new workloads to run on Snowflake. The single engine approach translates into a single experience—from one consistent pricing model to an integrated approach combining performance, security, governance, and the foundation to seamlessly enable cross-region or cross-cloud scenarios.