Looker has introduced a new feature called `publish_as_db_view` in its version 7, which solves the issue of Persistent Derived Tables (PDTs) breaking downstream systems due to name changes. The new feature creates a new view that acts as a redirect, allowing stable naming and enabling other services to reference the table without fear of breaking. To use this feature, admins need to add `publish_as_db_view: yes` to their Looker View's derived_table section and ensure they're using either `sql_trigger_value` or `datagroup_trigger` to determine when PDTs should be regenerated. Once enabled, admins can rebuild their view by navigating to it in Explore and triggering a rebuild. The new view can then be referenced directly from SQL without worrying about breaking downstream systems.