# Database Saving **URL:** \ **Category:** Ask for Help\ **Created:** [January 13, 2025, 9:20pm UTC](https://community.glideapps.com/t/database-saving/79177 "2025-01-13T21:20:38Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![LAM\_DO](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/lam_do/32/79260_2.png) [@LAM\_DO](https://community.glideapps.com/u/LAM_DO)\ **Post date:** [January 13, 2025, 9:20pm UTC](https://community.glideapps.com/t/database-saving/79177/1 "2025-01-13T21:20:38Z")
Can anyone who has experience to deal with store data time by time tell me what to do. There is around 80-100 sales a day per location. Is that a good way to combine sales data into Json and store it into text field or even array field so I can save more row and then I will be able to pull it up later on when I do a payroll. Or do you have the better method please share. I’m appreciated! And also I have 10,000 clients and 20,000 giftcard. Is it better to save it in Big Table or use in external app. Because it it static data and it also cost row. How do I manage that in the best way? ---
**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:** [January 13, 2025, 10:52pm UTC](https://community.glideapps.com/t/database-saving/79177/2 "2025-01-13T22:52:42Z")
I don’t think you should do that. I would rather pay more to have higher cap and be able to insert more rows, than store paginated JSON object in rows with each row having a JSON of 100 “subrows”. You will see that it would became hard to maintain… ---
**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:** [January 13, 2025, 10:53pm UTC](https://community.glideapps.com/t/database-saving/79177/3 "2025-01-13T22:53:30Z")
20k row for gift card is near 25k. You should use big tables! Are you planing on using row owners to limit the access to those gift cards? ---
**Author:** ![LAM\_DO](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/lam_do/32/79260_2.png) [@LAM\_DO](https://community.glideapps.com/u/LAM_DO)\ **Post date:** [January 14, 2025, 12:34am UTC](https://community.glideapps.com/t/database-saving/79177/4 "2025-01-14T00:34:48Z")
Hi Max, Right now everything is in 1 app. The concept is the POS role has Admin Role. They can access the entire of everything. Others has email role and location role based on their position. So in my mind now I will changes Sales and Giftcard and Customers table Big Table in 1 team business plan. I will creat another team with Maker plan to have unlimit user to access the same tables is that possible? ---
**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:** [January 14, 2025, 12:50am UTC](https://community.glideapps.com/t/database-saving/79177/5 "2025-01-14T00:50:35Z")
You can’t use the same Glide Table across teams unfortunately. Google sheet would work under 25k rows, but if you update a row on one GS from Glide Data Editor, the other team will consume one update for each sync. So can go up very quickly. Here is a post that you might like reading: > [@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… ---
**Author:** ![system](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/system/32/53398_2.png) [@system](https://community.glideapps.com/u/system)\ **Post date:** [January 21, 2025, 12:50am UTC](https://community.glideapps.com/t/database-saving/79177/6 "2025-01-21T00:50:42Z")
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.