Data branching®

Overview

The PlanetScale Data Branching® feature allows you to create isolated copies of your database that include both the schema and data. This differs from our regular branching feature, which only includes the schema.

Enable the Data Branching® feature for your database.

Before you can use the feature, you have to enable it in your database settings page.

1. Navigate to the database that you’d like to enable.
2. Click on the “Settings” link in the header navigation bar.
3. Scroll to the option with the text “Enable Data Branching®“
4. Enable this option and click “Save database settings”.

Create a new seeded branch

1. After enabling the Data Branching feature, navigate to the dashboard page of the database.
2. Clicking on “New Branch” should now offer an option to select “Seed Data”. - None — Creates a database branch with only the schema copied to the new branch. - From most recent backup — Creates a database branch with both the schema and data from the latest backup of the Base branch.

   

Branching off of a production branch and seeding it with data can incur additional charges, as branches seeded from production are treated as production branches instead of development branches. See question 5 in the FAQ below for more information.

3. Once you’ve selected an option, click “Create branch” to create a new branch.

FAQ

Can I pick which backup is used for the new branch?

PlanetScale picks the latest backup so that your new branch has the latest dataset to work with.

Can I pick which tables are copied into the new branch?

PlanetScale seeds the new branch with all the schema & data from the base branch. We do not offer a way to filter out data or schema when creating a new branch.

Is data in the new branch kept up to date with changes to the base branch?

PlanetScale does not provide data syncing between a production branch and a development branch.

When I merge my deploy request, will any data changes be merged back to the base branch?

PlanetScale does not provide data syncing between a production branch and a development branch.

Will enabling the Data Branching® feature affect my billing?

Yes, it can. If you are branching and seeding from a development branch, the new branch will count towards your development branch usage hours in the same way that regular branching does, but because you’re seeding it with data, it will also be billed for storage.

However, if you branch and seed from a production branch, the new branch will be created as a production branch at the same resource size as the source production branch, and will therefore be billed at that size. It will also be seeded with the production data and include the 2 default production replicas, so you will be charged for the storage as well for however long the branch stays running.

For example, if you are branching off a PS-80 production branch with 100 GB of storage, and you seed the new branch with that source production branch’s data, you will be billed for the new seeded branch as follows:

• PS-80 — $179
• 100 GB — ($0.50 \* 100 GB) \* 3 replicas =$135

We spin the new branch up using the same resource size as the production branch to ensure that large datasets initialize correctly and efficiently. After initialization, you may downgrade the branch size on the Clusters page. All billing is prorated, so you will only be charged for the time your seeded branch is live. To avoid incurring extra charges, be sure to downsize your seeded branch, and delete it once you’re done using it

Need help?

Get help from the PlanetScale Support team, or join our GitHub discussion board to see how others are using PlanetScale.