# Glide Big Tables - pricing

**URL:** <https://community.glideapps.com/t/glide-big-tables-pricing/58578>\
**Category:** Ask for Help\
**Tags:** big-tables\
**Created:** [February 28, 2023, 12:43pm UTC](https://community.glideapps.com/t/glide-big-tables-pricing/58578 "2023-02-28T12:43:39Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![Eric\_Penn](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/eric_penn/32/73888_2.png) [@Eric\_Penn](https://community.glideapps.com/u/Eric_Penn)\
**Post date:** [April 5, 2023, 4:02pm UTC](https://community.glideapps.com/t/glide-big-tables-pricing/58578/21 "2023-04-05T16:02:54Z")

</div>

What I’d like to do is store 1 million rows in BT but only pull a small amount of them into a glide table. Then I could do relations and rollups over computed columns.

In my current situation I use a filter in GSheet but because GSheet can’t store millions of rows I have to segment my app for each customer.

---

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [April 5, 2023, 4:03pm UTC](https://community.glideapps.com/t/glide-big-tables-pricing/58578/22 "2023-04-05T16:03:21Z")

</div>

> [@gvalero](#):
>
> To be honest, I haven’t tested Glide with Big Tables but according to what I have seen in videos, you **can create queries internally**.

No, you can’t.  
(I have tested with Big Tables)

> [@gvalero](#):
>
> This pic by @Eric_Penn is an example (but again, I can’t confirm if this is **optional or mandatory** )

The pic shows a Big Query table. Yes, Big Query tables are populated by querying a Google Big Query database.  
(I’ve also tested with those).

---

<div class="post-metadata">

**Author:** ![Eric\_Penn](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/eric_penn/32/73888_2.png) [@Eric\_Penn](https://community.glideapps.com/u/Eric_Penn)\
**Post date:** [April 5, 2023, 4:04pm UTC](https://community.glideapps.com/t/glide-big-tables-pricing/58578/23 "2023-04-05T16:04:48Z")

</div>

Time is on my side so if you are saying it’s not possible (yet) I would wait and keep everything under Glides umbrella… else I will move to BQ.

---

<div class="post-metadata">

**Author:** ![Uzo](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/uzo/32/22639_2.png) [@Uzo](https://community.glideapps.com/u/Uzo)\
**Post date:** [April 5, 2023, 4:06pm UTC](https://community.glideapps.com/t/glide-big-tables-pricing/58578/24 "2023-04-05T16:06:45Z")

</div>

😅

---

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [April 5, 2023, 4:07pm UTC](https://community.glideapps.com/t/glide-big-tables-pricing/58578/25 "2023-04-05T16:07:44Z")

</div>

> [@Eric\_Penn](#):
>
> What I’d like to do is store 1 million rows in BT but only pull a small amount of them into a glide table. Then I could do relations and rollups over computed columns.
> 
> In my current situation I use a filter in GSheet but because GSheet can’t store millions of rows I have to segment my app for each customer.

Yeah, I’ve seen your crazy setup 😛  
I think Big Query is probably the direction you need to be taking.  
Then you can store all your data in one giant Big Query database, and each customer App can pull in the data for that App using a query.  
Although - Big Query does have similar [limitations](https://www.glideapps.com/docs/reference/data-sources/bigquery#limitations-of-big-query) as Big Tables. So that might be a problem. But I do know that Glide are working to remove some of those limitations, so in your case it might be best to wait a while and see how things evolve 🤷‍♂️

---

<div class="post-metadata">

**Author:** ![Uzo](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/uzo/32/22639_2.png) [@Uzo](https://community.glideapps.com/u/Uzo)\
**Post date:** [April 5, 2023, 4:12pm UTC](https://community.glideapps.com/t/glide-big-tables-pricing/58578/26 "2023-04-05T16:12:03Z")

</div>

Why bother with BQ or BT… if we have fetch json and javascript columns lol

---

<div class="post-metadata">

**Author:** ![gvalero](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/gvalero/32/1037_2.png) [@gvalero](https://community.glideapps.com/u/gvalero)\
**Post date:** [April 5, 2023, 4:13pm UTC](https://community.glideapps.com/t/glide-big-tables-pricing/58578/27 "2023-04-05T16:13:07Z")

</div>

So… when do we need to use/choose BT vs BQ? 🙄

---

<div class="post-metadata">

**Author:** ![Eric\_Penn](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/eric_penn/32/73888_2.png) [@Eric\_Penn](https://community.glideapps.com/u/Eric_Penn)\
**Post date:** [April 5, 2023, 4:13pm UTC](https://community.glideapps.com/t/glide-big-tables-pricing/58578/28 "2023-04-05T16:13:32Z")

</div>

It’s wayyyy less crazy now thanks to you and others in the community who have taught me best practices. I will take your advice again and wait to see how things evolve.

While I’m waiting I’ll have a go at BQ and educate myself further.

---

<div class="post-metadata">

**Author:** ![Eric\_Penn](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/eric_penn/32/73888_2.png) [@Eric\_Penn](https://community.glideapps.com/u/Eric_Penn)\
**Post date:** [April 5, 2023, 4:17pm UTC](https://community.glideapps.com/t/glide-big-tables-pricing/58578/29 "2023-04-05T16:17:19Z")

</div>

I receive ~1000 rows a day via csv’s in email attachments. The delivery method is not under my control so that’s where I start.

I need to store those rows somewhere 🤷‍♂️

---

<div class="post-metadata">

**Author:** ![Uzo](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/uzo/32/22639_2.png) [@Uzo](https://community.glideapps.com/u/Uzo)\
**Post date:** [April 5, 2023, 4:18pm UTC](https://community.glideapps.com/t/glide-big-tables-pricing/58578/30 "2023-04-05T16:18:26Z")

</div>

You can store in json, up to 20k rows per cell

---

<div class="post-metadata">

**Author:** ![gvalero](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/gvalero/32/1037_2.png) [@gvalero](https://community.glideapps.com/u/gvalero)\
**Post date:** [April 5, 2023, 4:18pm UTC](https://community.glideapps.com/t/glide-big-tables-pricing/58578/31 "2023-04-05T16:18:46Z")

</div>

I know your point but the problem with using a fetch and json payload is that you need to create a helper table (manually) to transponed the data.

Instead, a native query in BQ is able to create a dynamic table ready to be used.

---

<div class="post-metadata">

**Author:** ![Uzo](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/uzo/32/22639_2.png) [@Uzo](https://community.glideapps.com/u/Uzo)\
**Post date:** [April 5, 2023, 4:19pm UTC](https://community.glideapps.com/t/glide-big-tables-pricing/58578/32 "2023-04-05T16:19:35Z")

</div>

You create it once… Then just reuse it

---

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [April 5, 2023, 4:20pm UTC](https://community.glideapps.com/t/glide-big-tables-pricing/58578/33 "2023-04-05T16:20:50Z")

</div>

> [@gvalero](#):
>
> So… when do we need to use/choose BT vs BQ? 🙄

Big Tables is a native Glide Data source. It’s just like regular Glide Tables, except… bigger 🙂 It is different in that instead of all rows being loaded immediately to the user device, rows are loaded as they are needed. It also has some limitations around data aggregation, which are documented.

Big Query is what Glide refer to as a “queryable data source”. Data is stored in Google Big Query, and your Glide Tables are defined and populated by queries that you write against that data.

---

<div class="post-metadata">

**Author:** ![Uzo](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/uzo/32/22639_2.png) [@Uzo](https://community.glideapps.com/u/Uzo)\
**Post date:** [April 5, 2023, 4:21pm UTC](https://community.glideapps.com/t/glide-big-tables-pricing/58578/34 "2023-04-05T16:21:53Z")

</div>

That is my technique for the unlimited rows in glide… But i don’t need bt or bq

---

<div class="post-metadata">

**Author:** ![gvalero](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/gvalero/32/1037_2.png) [@gvalero](https://community.glideapps.com/u/gvalero)\
**Post date:** [April 5, 2023, 4:27pm UTC](https://community.glideapps.com/t/glide-big-tables-pricing/58578/35 "2023-04-05T16:27:18Z")

</div>

> You create it once… Then just reuse it

Of course 🤣

but here we need to be efficient, if I create a helper table with 1000 rows and 50 columns (thinking in the worst case) and my payload returns most cases 20-40 rows, we are wasting data and load unnecessary info.

---

<div class="post-metadata">

**Author:** ![Eric\_Penn](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/eric_penn/32/73888_2.png) [@Eric\_Penn](https://community.glideapps.com/u/Eric_Penn)\
**Post date:** [April 5, 2023, 4:28pm UTC](https://community.glideapps.com/t/glide-big-tables-pricing/58578/36 "2023-04-05T16:28:15Z")

</div>

I think I get what you’re selling. I use a technique where I adapted the trebuchet method and the miracle method to save on rows in other areas of my app. Essentially I have a few columns which store csv’s and then I explode those rows by transposing them into a helper table.

Your way does sound more effective

---

<div class="post-metadata">

**Author:** ![Uzo](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/uzo/32/22639_2.png) [@Uzo](https://community.glideapps.com/u/Uzo)\
**Post date:** [April 5, 2023, 4:28pm UTC](https://community.glideapps.com/t/glide-big-tables-pricing/58578/37 "2023-04-05T16:28:48Z")

</div>

You dont waste anything, my apps are using only 20 rows, to operate on millions, and are faster than Glide

---

<div class="post-metadata">

**Author:** ![Uzo](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/uzo/32/22639_2.png) [@Uzo](https://community.glideapps.com/u/Uzo)\
**Post date:** [April 5, 2023, 4:32pm UTC](https://community.glideapps.com/t/glide-big-tables-pricing/58578/38 "2023-04-05T16:32:03Z")

</div>

Ok… I have to run… Before they ban me again… 😉

---

<div class="post-metadata">

**Author:** ![gvalero](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/gvalero/32/1037_2.png) [@gvalero](https://community.glideapps.com/u/gvalero)\
**Post date:** [April 5, 2023, 4:37pm UTC](https://community.glideapps.com/t/glide-big-tables-pricing/58578/39 "2023-04-05T16:37:40Z")

</div>

Thanks!

and how can we create a BT from Glide Editor? There is no such option in the list. 🤭

![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/6/a/6a7c6ab05059f2a44600a6d3a1d21cc5fd516ec3.png)

---

<div class="post-metadata">

**Author:** ![Eric\_Penn](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/eric_penn/32/73888_2.png) [@Eric\_Penn](https://community.glideapps.com/u/Eric_Penn)\
**Post date:** [April 5, 2023, 4:40pm UTC](https://community.glideapps.com/t/glide-big-tables-pricing/58578/40 "2023-04-05T16:40:38Z")

</div>

You need to request access. There is a link at the bottom of this page under FAQ.

> **[Glide • Big Tables](https://www.glideapps.com/docs/reference/data-sources/big-tables)**
>
> Scale your app with up to 10 million rows of data.

@Sean_Martin could you please help our friend @gvalero with Big Table access?

[Previous page](https://community.glideapps.com/t/glide-big-tables-pricing/58578.md?page=1)

[Next page](https://community.glideapps.com/t/glide-big-tables-pricing/58578.md?page=3)
