Issues after migrating SCOM 2012 Database

As this post is being written, the official MS procedure to migrate a SCOM 2012 operational Database is incomplete. See the official procedure here:
There are two extra steps that you have to do. One I’ve documented in a previous post:

You need to change the values in the key below. Otherwise, you’ll have issues and trying to apply SP1, for example. It tries to talk to you old server and can’t figure out the upgrade scenario.

HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft Operations Manager3.0SetupDatabaseServerNameclip_image002
This used to be documented in the original 2007 database move guide. Don’t know why it was removed.

On step seven, Microsoft mentions one occurrence of the server name under the Cmdb tag:clip_image004

Actually, the server name also appears in the ConfigStore tag and if you don’t change it, you’ll keep getting errors in the login with invalid login attempts against the old server.clip_image005

Update: there is actually another step you should do avoid the funky (useless)SQL messages you see when something SQL related happens. Please see the article below from Marnix Wolf:

Hope this helps!