# Cleanup SQL files after deploy

**URL:** <https://community.kinsta.com/t/cleanup-sql-files-after-deploy/414>\
**Category:** Feature Requests\
**Created:** [February 22, 2021, 1:07am UTC](https://community.kinsta.com/t/cleanup-sql-files-after-deploy/414 "2021-02-22T01:07:47Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![greghunt](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/greghunt/32/127_2.png) [@greghunt](https://community.kinsta.com/u/greghunt)\
**Post date:** [February 22, 2021, 1:07am UTC](https://community.kinsta.com/t/cleanup-sql-files-after-deploy/414/1 "2021-02-22T01:07:47Z")

</div>

It seems that when using the “push to staging” feature, an SQL dump is made locally and on the remote. It would be nice if these files were cleaned up after they’ve been used. Fortunately, the sql on the remote isn’t web accessible, but it still doesn’t feel good having my DB in my web root.

---

<div class="post-metadata">

**Author:** ![michael](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/michael/32/31_2.png) [@michael](https://community.kinsta.com/u/michael)\
**Post date:** [February 22, 2021, 4:07pm UTC](https://community.kinsta.com/t/cleanup-sql-files-after-deploy/414/2 "2021-02-22T16:07:48Z")

</div>

Thanks for the feature request @greghunt !