This document and its companion document Amazon Redshift to BigQuery SQL translation reference are part of the enterprise data warehouse (EDW) migration initiative.
This document highlights technical differences and provides guidance on migrating from the Redshift data warehouse to BigQuery, Google's fully managed, petabyte-scale data warehouse. The document specifically targets migrations of EDW and online analytical processing (OLAP) use cases, which use BigQuery's table scans. If you need online transaction processing (OLTP) behavior like single-row updates or inserts, consider a database designed to support OLTP use cases such as Cloud SQL.
|Purpose||To provide high-level guidance for organizations that are migrating Redshift to BigQuery.|
|Intended audience||Enterprise architects, DBAs, application developers, and IT security.|
|Key assumptions||That the audience is familiar with Redshift and is looking for guidance on transitioning to BigQuery.|
Objectives of this guide
- Provide high-level guidance to organizations migrating from Redshift to BigQuery.
- Show ways organizations can rethink their existing data pipelines to get the most out of BigQuery.
- Compare the architectures of BigQuery and Redshift to help organizations map features and capabilities during migration. Our goal is to show you new capabilities available to your organization through BigQuery, not to map features one-to-one with Redshift.
Nonobjectives of this guide
- Provide detailed instructions for all activities required to migrate from Redshift to BigQuery.
- Present solutions for every use case of Redshift in BigQuery.
- Replace our BigQuery documentation or act as a substitute for training on big data. We strongly recommend that you take our Big Data and Machine Learning classes and review our extensive documentation prior to, or in conjunction with, this guide.
To read the full document, click the button: