Hello @habyphilipose!

I agree with @kerem. However, Databricks now supports an auto-drop behaviour using the pipeline configuration "pipelines.dropInactiveTables": "true". When enabled, this will automatically remove MV/STs from the catalog during the next pipeline update, only if those tables are no longer defined in the pipeline code.