What I did was spin up a separate VM to act solely as the FSDB. This box is separate from my NPM/NTA front-end box and separate from my SQL box. It's very, very simple, low-touch, and has worked flawlessly for me since day one. I understand that being able to spin up a box just for this purpose is a luxury, but it has worked very well.
If you did need to co-locate the FSDB with either the front-end/console or SQL, I might suggest the front-end of those two options. If you're able, dedicate a separate volume for the FSDB and go from there. The nice thing about the FSDB data is that there isn't a lot of change/churn (hence SW's decision to separate out the NTA data in the first place to prevent excessive SQL hammering).