# Database recreate performance

**URL:** <https://forum.duplicati.com/t/database-recreate-performance/5999>\
**Category:** Developer\
**Created:** [January 14, 2019, 9:37pm UTC](https://forum.duplicati.com/t/database-recreate-performance/5999 "2019-01-14T21:37:32Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![JonMikelV](https://forum.duplicati.com/letter_avatar_proxy/v4/letter/j/439d5e/32.png) [@JonMikelV](https://forum.duplicati.com/u/JonMikelV)\
**Post date:** [January 15, 2019, 9:11pm UTC](https://forum.duplicati.com/t/database-recreate-performance/5999/2 "2019-01-15T21:11:45Z")

</div>

For the record, the way this SQL is built dynamically makes it very difficult to optimize things - not just the SQL but also the calling method (I suspect we’re not benefiting from store execution plans on these repeated calls).

Testing (and ultimately final code) for this may entail “hard coded” SQL. If it improves performance enough, that should be a valid reason to suffer through the pain of maintaining it.

---

_[View the full topic](https://forum.duplicati.com/t/database-recreate-performance/5999)._
