You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This script is incredibly useful and I've used it many times. However, I encountered a problem and I still couldn't understand how to solve it as the query is quite complex.
I made a data model for the DDL of my entire Redshift DW and most of the tables have a correct ddl. But for some of them I have the current ddl (table creation and comments) but also the older instructions. Instead of having a single table creation with comments, I have the current query as well as the oldest table update.
Is there any chance that the problem lies in the fact that the sql script is retrieving the entire history of DDL's instead of just the most recent one? Maybe the timestamp range which is chosen...
Hope you guys can help me. I am not yet an expert on Redshift.
The text was updated successfully, but these errors were encountered:
Thanks for the information. Are you able to reproduce this with a new table? Or was there a specific change to those tables that are showing duplicates?
Hello everyone,
Thank you in advance for your help.
This script is incredibly useful and I've used it many times. However, I encountered a problem and I still couldn't understand how to solve it as the query is quite complex.
I made a data model for the DDL of my entire Redshift DW and most of the tables have a correct ddl. But for some of them I have the current ddl (table creation and comments) but also the older instructions. Instead of having a single table creation with comments, I have the current query as well as the oldest table update.
Is there any chance that the problem lies in the fact that the sql script is retrieving the entire history of DDL's instead of just the most recent one? Maybe the timestamp range which is chosen...
Hope you guys can help me. I am not yet an expert on Redshift.
The text was updated successfully, but these errors were encountered: