Automated, regular movement of old data from Google sheet to a more permanent cloud database?

[edmund_chan]

Is there a good or/and common practice on how to store data more permanently beyond Google sheets? I know that Google sheets can take in lots of rows and columns, and we can lock it to prevent accidental changes. It still needs to be maintain so that the AppSheet app can sync faster if the Google sheet contains just the relevant data, and a separate database that contains historical data could be very helpful in further analysis.

[LeventK]

Guide on How To Create a Community Post Tips & Tricks 💡

Dear valuable members and users, For a long time I’m seeing a lot of multiple and concurrent posts, posts like novels seeming to aim the Pulitzer Price, exactly the same questions by the same user but paraphrased/re-phrased etc. Being a dedicated community member and an AppSheet developer who is reading around 2.5K posts per day, I urged myself to tip on some good advice and best practice BEFORE posting something in the community: #1 - APPSHEET DOCUMENTATION AppSheet has a very good help do…

[Steve]

help.appsheet.com

Scaling Using Data Partitions

How to use data partitions to improve performance at scale.

[edmund_chan]

Thank you very much Steve. This is very helpful and specific. I noted an earlier reply to go through AppSheet documentation too. I will do so. Sorry to trouble everyone.

Edmund Chan

[edmund_chan]

Just to add, we can do a time-based slice with partitions so that we don’t keep seeing old data on our apps. We don’t need to transfer data out from google sheets, which is very useful as we can just apply other google cloud tools like Google Data Studio for further analysis on historical data.