# Early Access: Glide Big Tables 💪

**URL:** <https://community.glideapps.com/t/early-access-glide-big-tables/58312>\
**Category:** General\
**Created:** [February 22, 2023, 8:19pm UTC](https://community.glideapps.com/t/early-access-glide-big-tables/58312 "2023-02-22T20:19:47Z")\
**Posts on this page:** 9\
**Page:** 2

<div class="post-metadata">

**Author:** ![Miller](https://avatars.discourse-cdn.com/v4/letter/m/bbce88/32.png) [@Miller](https://community.glideapps.com/u/Miller)\
**Post date:** [June 20, 2023, 1:41pm UTC](https://community.glideapps.com/t/early-access-glide-big-tables/58312/21 "2023-06-20T13:41:14Z")

</div>

This! I just realized this after creating my app using only Big Tables… When will we be able to use lookup and rollup columns on relations in Big Tables??? Very key feature

---

<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:** [June 20, 2023, 1:48pm UTC](https://community.glideapps.com/t/early-access-glide-big-tables/58312/22 "2023-06-20T13:48:01Z")

</div>

You can do both now. The only caveat is that the target column in the Big Table cannot be a computed column.

---

<div class="post-metadata">

**Author:** ![Miller](https://avatars.discourse-cdn.com/v4/letter/m/bbce88/32.png) [@Miller](https://community.glideapps.com/u/Miller)\
**Post date:** [June 20, 2023, 2:04pm UTC](https://community.glideapps.com/t/early-access-glide-big-tables/58312/23 "2023-06-20T14:04:00Z")

</div>

Oh ok thanks. Ya that’s exactly what I was trying to do - a rollup sum of a formula in a relation… any workaround?

---

<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:** [June 20, 2023, 2:07pm UTC](https://community.glideapps.com/t/early-access-glide-big-tables/58312/24 "2023-06-20T14:07:17Z")

</div>

The only workaround would to write the result of the formula into a non-computed column, then you could rollup on that.

---

<div class="post-metadata">

**Author:** ![Miller](https://avatars.discourse-cdn.com/v4/letter/m/bbce88/32.png) [@Miller](https://community.glideapps.com/u/Miller)\
**Post date:** [June 20, 2023, 2:21pm UTC](https://community.glideapps.com/t/early-access-glide-big-tables/58312/25 "2023-06-20T14:21:04Z")

</div>

Do you know if this will be changed for Big Tables in the future?

---

<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:** [June 20, 2023, 2:47pm UTC](https://community.glideapps.com/t/early-access-glide-big-tables/58312/26 "2023-06-20T14:47:48Z")

</div>

I think it’s very unlikely. Computed columns (even in Big Tables) are computed client side, so in order to make this work the entire contents of the Big Table would first need to be loaded onto the users device.

---

<div class="post-metadata">

**Author:** ![Miller](https://avatars.discourse-cdn.com/v4/letter/m/bbce88/32.png) [@Miller](https://community.glideapps.com/u/Miller)\
**Post date:** [June 20, 2023, 3:02pm UTC](https://community.glideapps.com/t/early-access-glide-big-tables/58312/27 "2023-06-20T15:02:18Z")

</div>

Ok I’ve been doing all my apps with Airtable, but what I’m trying to build could easily exceed the rows limit. I’ve never played with BigQuery. Should I look into that?

---

<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:** [June 20, 2023, 3:13pm UTC](https://community.glideapps.com/t/early-access-glide-big-tables/58312/28 "2023-06-20T15:13:29Z")

</div>

I think it depends on your particular use case. One downside with Big Query is that you can’t do dynamic queries like you can with Big Tables. It’s more suited to a situation where you have a very large data source and you want to summarise it. The other thing is that it is read-only from Glide.

---

<div class="post-metadata">

**Author:** ![Miller](https://avatars.discourse-cdn.com/v4/letter/m/bbce88/32.png) [@Miller](https://community.glideapps.com/u/Miller)\
**Post date:** [June 20, 2023, 7:31pm UTC](https://community.glideapps.com/t/early-access-glide-big-tables/58312/29 "2023-06-20T19:31:01Z")

</div>

Thanks for all your help. I am going to try just regular Glide Tables and then when those fill up, move older data to Big Tables

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