<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>bigquery on Eric&#39;s Note</title>
    <link>https://eric.nz/tags/bigquery/</link>
    <description>Recent content in bigquery on Eric&#39;s Note</description>
    <image>
      <url>https://eric.nz/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</url>
      <link>https://eric.nz/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</link>
    </image>
    <generator>Hugo -- gohugo.io</generator>
    <lastBuildDate>Mon, 24 Mar 2025 10:48:00 +0000</lastBuildDate><atom:link href="https://eric.nz/tags/bigquery/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Google BigQuery Best Practices</title>
      <link>https://eric.nz/posts/google-bigquery-best-practices/</link>
      <pubDate>Mon, 24 Mar 2025 10:48:00 +0000</pubDate>
      
      <guid>https://eric.nz/posts/google-bigquery-best-practices/</guid>
      <description>Right way to explore tables in BigQuery This LinkedIn Post by Yingjun Wu ( link ) had show cased a ridiculous case of BigQuery pricing model.
BigQuery charges based on the amount of data referenced, not by the amount of data processed. This means that even you used a LIMIT keyword to limit the number of rows returned, BigQuery will still charge you the amount of data query referenced.
The right way to explore tables in BigQuery is to use TABLESAMPLE clause to sample the data.</description>
    </item>
    
  </channel>
</rss>
