How emigrate an information warehouse to BigQuery

How emigrate an information warehouse to BigQuery

by



Has your knowledge staff outgrown its on-premise conventional knowledge warehouse? Are you in search of a system to retailer knowledge that’s safe, scalable, and price efficient? On this episode of Architecting with Google Cloud, Priyanka Vergadia speaks with Gary Morreale, the Director of Information Companies from Independence Blue Cross about how his staff migrated from Terradata to Bigquery on Google Cloud Platform. Hear as Gary Morreale discusses his staff’s large endeavor on migrating dataware to BigQuery.

Chapters:
0:00 – Intro
1:00 – What are the challenges with an on-premises Information Warehouse
1:48 – Information warehouse migration technique for Terabytes of information
2:42 – Information warehouse migration structure
4:50 – Structure for knowledge analytics: how do knowledge science groups use the info
6:40 – What’s past knowledge warehouse migration
7:20 – Wrap Up

Architecting with Google Cloud playlist → https://goo.gle/3g7xAC9
Subscribe to Google Cloud Tech → https://goo.gle/GoogleCloudTech

#ArchitectingWithGoogleCloud

product: Cloud – Basic; fullname: Priyanka Vergadia;

supply

12 thoughts on “How emigrate an information warehouse to BigQuery”

  4. We want to see real examples. Make an app with, java/node etc with front in react/angular add a DB and play different scenarios. It's full internet of GC theory…but no real example.

    Reply

  6. As a cost effective solution, didn't we should store data in hive-gs bucket for stage and core layer data and final data should be pushed to bigquery for information layer. Please suggest

    Reply

Leave a Comment