# Incremental auto-vacuum

**URL:** <https://discuss.zetetic.net/t/incremental-auto-vacuum/2064>\
**Category:** SQLCipher\
**Created:** [March 31, 2017, 11:28am UTC](https://discuss.zetetic.net/t/incremental-auto-vacuum/2064 "2017-03-31T11:28:15Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![aleksandarkostic](https://avatars.discourse-cdn.com/v4/letter/a/bbe5ce/32.png) [@aleksandarkostic](https://discuss.zetetic.net/u/aleksandarkostic)\
**Post date:** [March 31, 2017, 11:28am UTC](https://discuss.zetetic.net/t/incremental-auto-vacuum/2064/1 "2017-03-31T11:28:15Z")

</div>

Does anybody has experience with vacuum strategies? Since full VACUUM could introduce some potentially risky situation, we decided to use auto-vacuum which we would trigger from application. Does call frequency to this has any drawbacks in the respect of sqlcipher?  
Thanks.

---

<div class="post-metadata">

**Author:** ![sjlombardo](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.zetetic.net/sjlombardo/32/3_2.png) [@sjlombardo](https://discuss.zetetic.net/u/sjlombardo)\
**Post date:** [April 4, 2017, 7:56pm UTC](https://discuss.zetetic.net/t/incremental-auto-vacuum/2064/2 "2017-04-04T19:56:12Z")

</div>

Hello @aleksandarkostic we don’t have any specific recommendations regarding vacuum with SQLCipher. It sounds like you will be using incremental auto-vacuum, since you refer to triggering it from the application. The standard caveats apply, e.g. that auto-vacuum can result in greater fragmentation, pages aren’t compacted, freelist pages are moved to the end of the database, etc. It’s worth noting that that SQLCipher forces the database `secure_delete` option, so that either way, deleted data is zeroed out.