---
title: "Comment by Breanda Ramirs on \"Using BigQuery in the Google Cloud Console - GSP406\" | Hashnode"
description: "As someone who recently migrated legacy analytics, the section on separating storage and compute really hit home. It’s the feature that finally made our ad-hoc"
url: "https://hashnode.com/posts/using-bigquery-in-the-google-cloud-console-gsp406/67d7d2e999980261c49e572d/comment/69d68988dcda570fbd853b1d"
---

[Discussion](https://hashnode.com/posts/using-bigquery-in-the-google-cloud-console-gsp406/67d7d2e999980261c49e572d)

Comment [Using BigQuery in the Google Cloud Console - GSP406](https://hashnode.com/posts/using-bigquery-in-the-google-cloud-console-gsp406/67d7d2e999980261c49e572d)

[Breanda Ramirs](https://hashnode.com/@breanda)

[Apr 8](https://hashnode.com/posts/using-bigquery-in-the-google-cloud-console-gsp406/67d7d2e999980261c49e572d/comment/69d68988dcda570fbd853b1d)

As someone who recently migrated legacy analytics, the section on separating storage and compute really hit home. It’s the feature that finally made our ad-hoc query costs predictable. BigQuery's ability to scale them independently is a game-changer for budget-conscious teams.