- Newest
- Most votes
- Most comments
Redshift Automatic Table Optimization (ATO) uses the internal "table_id" identifier. As such ATO won't recognize the new table (after swapping) and won't automatically apply what what it had done previously. Of course not all is lost. You can create the new table_1_tmp by using "create table table_1_tmp (like table_1)". But to be sure that you want ATO to continue working on the new table, also do "ALTER TABLE table_1_tmp ALTER DISTSTYLE/SORTKEY AUTO".
More details. Redshift Automatic Table Optimization (ATO) uses the same mechanism as Redshift Advisor for sort and distribution key recommendations. With ATO, all recommendations are recorded in the SVV_ALTER_TABLE_RECOMMENDATIONS system table. If you take a closer look at its DDL:
https://docs.aws.amazon.com/redshift/latest/dg/r_SVV_ALTER_TABLE_RECOMMENDATIONS.html
You will notice that it ONLY contains the internal "table_id" NOT the "table_name".
Relevant content
- asked 2 years ago
- asked a year ago
- Accepted Answerasked 4 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago