Temporary Schema
urn:js:virtue:aspire:standard:23.1
TL;DR
The data modelling standards for the usage of the Temporary Schema in Aspire.
Definition
- The schema should solely be used for temporary and transient ETL tables - these are properties of Snowflake tables (so that change the setting of the object)
- Example objects created here - working data that will reside for the life of the data pipeline session only
- Views are the preference, tables are by exception
- Naming standard: Named after the job inserting data.
- Responsible/Accountable - Entire squad
- Reference: https://docs.snowflake.net/manuals/user-guide/tables-temp-transient.html
- Note the differences between temporary tables and transient tables
- Locked down to engineering teams only
- No Consuming Business User Access (e.g. data science, analytics). Use cases where access may be required is to support the internal transformation of data between the RDV, BDV and PL - in which case these schemas and data definitions should suffice (abstracting the internal transformations being performed away from the user)