# Glide Big Table Question

**URL:** https://community.glideapps.com/t/glide-big-table-question/78828
**Category:** Ask for Help
**Created:** [December 27, 2024, 8:41pm UTC](https://community.glideapps.com/t/glide-big-table-question/78828 "2024-12-27T20:41:59Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![MGA](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mga/32/50456_2.png) [@MGA](https://community.glideapps.com/u/MGA)
#### Post date: [December 27, 2024, 8:41pm UTC](https://community.glideapps.com/t/glide-big-table-question/78828/1 "2024-12-27T20:41:59Z")

</div>

I have not been working with Glide for some time now due to other professional priorities and was surprised to see that the default DB now is **Glide Big Table** , but it seems that **Glide Table** is still used for the **Users Table**.

Ist that correct? If yes, does that mean that there are actually 2 DBs at work?

I remember that one had to be careful with Glide Tables in terms of Security, using Row Owners etc. is that still necessary with Glide Big Tables, e.g. when a query is used to filter the data of a single user?

---

<div class="post-metadata">

### Author: ![MaximeBaker](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/maximebaker/32/80877_2.png) [@MaximeBaker](https://community.glideapps.com/u/MaximeBaker)
#### Post date: [December 27, 2024, 11:21pm UTC](https://community.glideapps.com/t/glide-big-table-question/78828/2 "2024-12-27T23:21:39Z")

</div>

> [@MGA](#):
>
> Ist that correct? If yes, does that mean that there are actually 2 DBs at work?

You can work with both of them yes !

> [@MGA](#):
>
> I remember that one had to be careful with Glide Tables in terms of Security, using Row Owners etc. is that still necessary with Glide Big Tables

Yes ! Row owners are still the only security feature to hide data with restricted access.

> [@MGA](#):
>
> when a query is used to filter the data of a single user?

Filters and visibility conditions are not security feature. You will be able to filter for easy filtering of data, but they are still downloadable if not restricted by row owners.

Here is a post I made that you might like to see:

> [@Security tip: Managing role-based permissions in Glide apps](https://community.glideapps.com/t/security-tip-managing-role-based-permissions-in-glide-apps/77854):
>
> If you’re using Glide apps and need secure control over user permissions, be aware that Glide’s visibility conditions (like showing or hiding buttons for certain roles) are not a security feature. While these conditions are helpful for managing the app’s appearance, they do not protect actions at the backend level. Key Points to Protect Your Data Row Owners for Data Protection: Enabling “Row Owners” is effective for securing individual records (for viewing, editing, and deleting), but it does…

---

<div class="post-metadata">

### Author: ![MGA](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mga/32/50456_2.png) [@MGA](https://community.glideapps.com/u/MGA)
#### Post date: [December 28, 2024, 6:23pm UTC](https://community.glideapps.com/t/glide-big-table-question/78828/3 "2024-12-28T18:23:55Z")

</div>

Thank you,

I was under the impression that **Glide Big Table** is more of a **Server DB** as **MS SQL** is.

Meaning that it only fetches data as queried.

e.g. SELECT fields FROM table WHERE id = whatever.

So, if one does not use Row Owners any User needs to potentially download **Millions of Rows**?

Cheers,

Mike

PS In my property management project I need to filter all **rows** belonging to a **property** belonging to a **owner**.

---

<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: [December 28, 2024, 6:46pm UTC](https://community.glideapps.com/t/glide-big-table-question/78828/4 "2024-12-28T18:46:51Z")

</div>

> [@MGA](#):
>
> So, if one does not use Row Owners any User needs to potentially download **Millions of Rows**?

No, rows are only sent to the user device as they are required.
