# Is it better to have one huge table with lots of data or several small tables?

**URL:** <https://community.glideapps.com/t/is-it-better-to-have-one-huge-table-with-lots-of-data-or-several-small-tables/69913>\
**Category:** Ask for Help\
**Created:** [January 23, 2024, 6:47pm UTC](https://community.glideapps.com/t/is-it-better-to-have-one-huge-table-with-lots-of-data-or-several-small-tables/69913 "2024-01-23T18:47:23Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Vikatchu](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/vikatchu/32/68714_2.png) [@Vikatchu](https://community.glideapps.com/u/Vikatchu)\
**Post date:** [January 23, 2024, 6:47pm UTC](https://community.glideapps.com/t/is-it-better-to-have-one-huge-table-with-lots-of-data-or-several-small-tables/69913/1 "2024-01-23T18:47:23Z")

</div>

Hello,  
is it better to have one huge table with lots of data or several small tables?  
I’m mainly asking about performance levels

---

<div class="post-metadata">

**Author:** ![nathanaelb](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/nathanaelb/32/43079_2.png) [@nathanaelb](https://community.glideapps.com/u/nathanaelb)\
**Post date:** [January 23, 2024, 6:57pm UTC](https://community.glideapps.com/t/is-it-better-to-have-one-huge-table-with-lots-of-data-or-several-small-tables/69913/2 "2024-01-23T18:57:23Z")

</div>

It’s hard to say. It’s probably best to test both scenarii and see which one provides the best performance. Taking into account that for a lot of data, you can also use high scaling tables (Glide Big Tables, SQL).

In general, I would make sure that the database is clearly structured: if you have object A and object B, better create 2 tables and create a relation between the table than start putting all objects in the same table.

Make sure tables are [normalized](https://community.glideapps.com/t/how-to-plan-out-your-database/68740/5).

There is a thread from a while back where someone explained that when a table becomes too big, it can be better to break up the table. This practice had a specific term, but I cannot remember the term nor can I locate the topic.