Looking for some thoughts on design table renaming. Looking for ways to avoid needed to the ability to rename tables online. Basically, we have a 2 tables. One is being used by the app for querying (active), and one is used by ETL to prepare the next data set (staging). Once the staging table is all loaded, logically, they rename the table from staging to active and active to staging, so the app sees the freshest data (I am glossing over details). How can we avoid that? The use case is we will load data into _temp_ table, rename target table to _bak_ table, rename _temp_ table to target table, and finally we will truncate _bak_ table. It is to minimize data access downtime while we refresh table data.