# Change CI drop schema command.

**URL:** <https://discourse.getdbt.com/t/change-ci-drop-schema-command/12356>\
**Category:** Help\
**Tags:** ci-cd, dbt-cloud, databricks\
**Created:** [March 7, 2024, 3:16am UTC](https://discourse.getdbt.com/t/change-ci-drop-schema-command/12356 "2024-03-07T03:16:52Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![jimconstable](https://sea2.discourse-cdn.com/flex020/user_avatar/discourse.getdbt.com/jimconstable/32/3740_2.png) [@jimconstable](https://discourse.getdbt.com/u/jimconstable)\
**Post date:** [March 7, 2024, 3:16am UTC](https://discourse.getdbt.com/t/change-ci-drop-schema-command/12356/1 "2024-03-07T03:16:53Z")

</div>

Is there any way I can affect the way dbt cloud drops the pull request CI schemas? I am using databricks unity catalog and a CI build schema can use quite a bit of storage. When that schema is dropped, the table storage is kept for 30 days in case the user want to undrop. This is unnecessary for a pull request schema and is making our storage requirements huge.