table and performance

[yasarcan]

There is something I am curious about: I have an application consisting of 40 pages. All in one table (gogle sheets). Does converting each sheet into a separate table slow down the application?

[Gustavo_Eduardo · Accepted solution]

I don’t know exactly how your application works, but after looking at your table structure and noticing that you store all the information in a single table, I have some concerns. Without concrete evidence, but at first glance, it seems that separating the data could be a better approach.

I suggest you look into fact tables and dimension tables, as well as the importance of references in database design. The goal is to achieve maximum data integrity, avoiding unnecessary redundancies and minimizing the number of empty fields. A well-structured design can make your application more efficient, flexible, and easier to maintain.

[Steve]

Not generally.

[Gustavo_Eduardo]

What you are saying is strange. Could you upload an image of your database? Hide the data you need (the important thing is to understand what you are referring to)

[Steve]

Yeah, it would be helpful to know what is in the one large table to help us offer better guidance.

[yasarcan]

hi. turned into resource planning software. but all the data is in one table. I want to separate it. Will this slow down the application? I collect and process 1000 lines of data daily. I admire appsheet.run

[Gustavo_Eduardo · Accepted solution]

I don’t know exactly how your application works, but after looking at your table structure and noticing that you store all the information in a single table, I have some concerns. Without concrete evidence, but at first glance, it seems that separating the data could be a better approach.

I suggest you look into fact tables and dimension tables, as well as the importance of references in database design. The goal is to achieve maximum data integrity, avoiding unnecessary redundancies and minimizing the number of empty fields. A well-structured design can make your application more efficient, flexible, and easier to maintain.

[yasarcan]

hi

[Gustavo_Eduardo]

So that's not just one table, but many. And from what I can see, you have a fairly well-formed structure. Even if I wanted to, I don't understand your question.

[Gustavo_Eduardo · Accepted solution]

I've reread your post, and I think I understand what you're saying. You have a single Google Sheets workbook, and within it, all your tables. If you're asking about the best approach, from a "storage" perspective, I’d recommend using a separate workbook for each table and not storing multiple sheets in the same workbook. This is because the maximum record limit per workbook will increase.

Please check this out: [Google Cloud Community link] (https://www.googlecloudcommunity.com/gc/Tips-Tricks/Appsheet-Standard-Naming-Protocol/m-p/775115#M98...).

In this protocol, I suggest using a Google Sheets workbook with one sheet per table, and that’s exactly what I do. When you want to migrate your application to SQL or from SQL to Google Sheets, the transition is always smoother when dealing with separate workbooks.

Can you do everything in a single workbook with multiple tabs? Yes, and it might be the most practical way (for development), but when it comes to implementation, having them separate is better in my experience.

Please note that there is also a slowdown in the experience when there are blank rows, which you could fix with a script. Follow this link to access a script, create your own or look at the protocol for the one I use.

Best regards.