Skip to content
hands-on lab

Dealing With Schema Changes in a Data Service

Difficulty: Intermediate
Duration: Up to 1 hour
Students: 803
Rating: 3.8/5
Start lab
On average, students complete this lab in20m
Get guided in a real environmentPractice with a step-by-step scenario in a real, provisioned environment.
Learn and validateUse validations to check your solutions every step of the way.
See resultsTrack your knowledge and monitor your progress.
About
Author

Description

Databases are extraordinarily powerful in managing sets of data, but what do we do when management wants to add/remove/modify something that code does? This lab is aimed at students with a moderate understanding of data engineering, and Python who want to understand how to update schemas to handle new features. We will walk through the changing requirements of a bug-tracking application and how to handle them.

Learning Objectives

Upon completion of this lab, you will be able to:

  • Evolve MySQL tables to handle schema changes
  • Learn how to update data models to meet changing requirements

Intended Audience

This lab is intended for:

  • Data engineers
  • Anyone needing to perform a schema migration on a relational database

Prerequisites

You should possess:

  • A moderate understanding of Python
  • A basic understanding of data engineering concepts

Updates

August 20th, 2025 - Resvoled issue connecting to the lab's notebook

June 24th, 2025 - Updated GCP VM instance image type

April 23rd, 2025 - Updated Cloud SQL DB version and screenshots to reflect the latest UI

August 8th, 2024 - Added password protection to notebook

Covered topics

Databases
Hands-on Lab UUID

Lab steps

0 of 2 steps completed.Use arrow keys to navigate between steps. Press Enter to go to a step if available.
  1. Signing In to the Google Cloud Console
  2. Opening the Lab's Jupyter Notebook in Google Cloud

Lab Rules