In my opinion… very smart move! We made the mistake of running our BES databases remotely for a short time and it totally bit us. Any latency, especially with the FillDB services, can and will cause cascading issues within a large BES environment.
Moving the databases themselves is relatively straight forward. I’d recommend leaving the existing remote DB instance in place, but turned down until the new, local instance is up and validated. Also, make sure that you update the database connections on your root BES server and any remote WebReports and/or WebUI instances.
That said, before you migrate your databases to the root BES server make sure that server has sufficient CPU, memory and the fastest storage I/O possible. Additionally, make sure that you fence the memory consumption of your SQL instance so that it doesn’t take too much away from the kernel and BES services.
Finally, make sure to review the “BigFix Capacity Planning, Performance, and Management Guide” that’s available at New White Paper: BigFix Capacity Planning, Performance, and Management Guide
I hope this helps! @cmcannady