# Nakama "migrate up" error

**URL:** <https://forum.heroiclabs.com/t/nakama-migrate-up-error/1316>\
**Category:** Local Setup\
**Tags:** getting-started\
**Created:** [January 23, 2021, 11:17pm UTC](https://forum.heroiclabs.com/t/nakama-migrate-up-error/1316 "2021-01-23T23:17:00Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![Mahdad-Baghani](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.heroiclabs.com/mahdad-baghani/32/465_2.png) [@Mahdad-Baghani](https://forum.heroiclabs.com/u/Mahdad-Baghani)\
**Post date:** [January 27, 2021, 1:00pm UTC](https://forum.heroiclabs.com/t/nakama-migrate-up-error/1316/6 "2021-01-27T13:00:57Z")

</div>

That’s exactly what I did. I didn’t move to a separate instance of cockroach DB until we wanted to do a closed test of our client and netcode; and I felt the need to separate the database due to some CPU spikes on the server which were caused by cockroachdb garbage collection. [Increase in CPU usage over time - #26 by novabyte](https://forum.heroiclabs.com/t/increase-in-cpu-usage-over-time/928/26)

---

_[View the full topic](https://forum.heroiclabs.com/t/nakama-migrate-up-error/1316)._
