Hello, We are planning on migrating our Bigfix/Webreports database which are already on external servers to a new server. I’ve reviewed the documentation and wondering if there are any gotcha’s anyone has come across.
We also have ILMT, SCA (running of a different external DB server) and not seeing if those would be impacted by bfenterprise, and webreports DB migrating to a new server.
Any hits or tips on other things to check before the DB migration to a new server?
We’re about to do this same task and have Inventory, ILMT, and SCA.
I have my plan to do “soon” but look forward to seeing what others comment.
SCA Data Source configured with REST API URL, BESReportinf database, BFEnterprise database - so after the migration make sure to update the data source - Performing initial set up and configuration
ILMT - haven't touched for a very long time.. from the documentation, it's the same case , after the migration you need to update the data source - IBM Documentation
Of course you will also need to update the WebUI configuration after the migration
I’m actually doing this this morning. Had no real issues in our sandbox a couple of weeks ago other than not following the complete instructions to use both the 32 and 64 version of ODBC. 
I’ll report back any gotchas later today.
We completed the migration yesterday. Here is what encounted. This is Big Fix 11.0.5 running on Windows 2016 (Next thing I deal to deal with)
After the imigration was finished and I restarted services I could not log into the console. Database logs showed “[sql server]login failed for user ''. Eventually discovered that the registry entry for Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\BigFix\Enterprise Server\Database was empty, so Big Fix did not know what username to user. Had to make a username and password entry here and then it started working. This did not happen on our non-prod environment
Afterward the migration, you need to run the WebUI Database (Enable/Update WebUI Database Configuration) FixLet in BES SUpport o get the WebUI to work. This is NOT in the database migration. Needed to also do this on non-prod as we didn;t catch it there.
Inventory data source needs to be setup again
IVR is not working correctly. Still looking at that one.
Just FYI, this part of it implies that when connecting to the old SQL server, the BigFix services and ODBC connection were using "WIndows Integrated Authentication", in which the Windows account used in the "Log On As" dialog in the Services applet was being used to authenticate to the SQL server; if you had to modify the registry to add a username in that key, then it is likely you are using 'SQL Authentication' (username/password) rather than Windows Integrated (Kerberos) to authenticate to the new SQL server.
Either way is acceptable in many environments, but you may wish to check with your DBA to see if this is working the way you all intended on the new server.
Edit: Editing the Registry to add the value there is certainly acceptable, but just FYI there are also BESAdmin commands available to change the username and password used to connect to the database, that manages the update to those registry values as well.
We are using SQL Authentication for both so I’m not quite sure what happened in our case. I’ll try to keep the BESadmin commands in mine but hope to not have to do this again for some time.