New message text here

Based on the available knowledge sources, there is no official recommendation from Elementary to regularly reset (drop) all tables in your BigQuery dataset. In fact, most guidance suggests that Elementary tables are designed to accumulate historical data for monitoring and reporting purposes, and regular resets are not a standard part of the workflow. However, some users do manually drop or truncate tables (especially temporary or very large tables) to manage storage and performance, particularly in development or sandbox environments. This is typically done as needed, not on a scheduled basis, and mainly to address specific issues like excessive storage usage or performance degradation. If you want to keep only recent data, you may need to implement your own cleanup process, as there is no built-in retention or automated cleanup for all tables in Elementary at this time. The Elementary team and community have discussed writing custom scripts or Airflow DAGs for this purpose, but again, this is not an official recommendation—just a workaround some teams use for their specific needs [Manual cleanup discussion](https://slack.com/archives/C02CTC89LAX/p1701764564340649) [Automated cleanup discussion](https://slack.com/archives/C02CTC89LAX/p1719390641107289). In summary: It is not officially recommended to reset Elementary tables on a regular basis, but you may choose to do so in certain scenarios (e.g., dev environments, storage concerns). If you need to retain only recent data, you will need to implement your own cleanup logic.