Now here's the really kind of mind blowing part. Even if you don't explicitly save a query as a permanent table by clicking on that Save as Table button or specifying a destination table. Once you run that query, any and all query, right? It actually, BigQuery behind the scenes, will store the results of that query in its own anonymous, temporary table. And the reason why it does that is so we can actually rerun that same query and get the benefit of pulling from query cache. Which as you saw in the Wikipedia example in the prior course, and a few of the other queries that we've been executing, is extremely fast. So let's hop back into the demo and then just take a look at what that looks like. Okay, so here I'm going to go ahead and remove the destination table. So this is just a one-off query that we're going to fire. I'm going to run the query, it's going to process 445 megabytes, and you can see that it's actually pulling directly from cache. So behind the scenes, there's a temporary table that exists that BigQuery has created on the backend. And that we can query from for 24 hours even without us knowing that we're querying and pulling from that temporary anonymous table. So that's the benefit for query cache. Much, much faster results and you're processing much fewer bytes. Okay, so here's the key lesson. All query results, again, are stored as a temporary or permanent table. And it's your choice whether or not, before the query runs or after the query runs, if you want to store it into that permanent table. But regardless, those results are going to be stored in a temporary table, and temporary tables last for about 24 hours. And that's the basis of query cache.
