---
title: "Comment by Hu xinya on \"Using BigQuery in the Google Cloud Console - GSP406\" | Hashnode"
description: "Great overview of getting started with BigQuery's speed and scale. For a follow-up, when working with large, frequently updated datasets, what's your recommende"
url: "https://hashnode.com/posts/using-bigquery-in-the-google-cloud-console-gsp406/67d7d2e999980261c49e572d/comment/69d65f2e7dd0829e82a36a3b"
---

[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)

[Hu xinya](https://hashnode.com/@xinya)

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

Great overview of getting started with BigQuery's speed and scale. For a follow-up, when working with large, frequently updated datasets, what's your recommended approach for structuring tables—would you lean towards partitioning by date or using clustering on other key columns for optimal performance and cost?