Advice on archiving old data and balancing sync performance against bloat when using google sheets

so i have been building an app that i expect to generate roughly 30,000 rows per year of data between 15 tables. about 18,000 rows will be in a single table. we have used slices where possible and have several tables which exist simply to house virtual columns that produce real time reports for the managers. they use enum lists to allow the selection of report filters, such as clients, date ranges, etc. i am using security filters so that standard users will not need to load these report tables. everyone will need to load the data tables in order to either enter or report on the data.

i am concerned about bloat and the 2 million cell limit from google and plan on archiving and emptying the data tables every 6 months. will emptying the tables cause the report menus and enum lists to go crazy? should i look into moving as much of the reporting features from virtual columns to spreadsheet formulas?

1 1 526
1 REPLY 1
Top Labels in this Space