A need may arise to move the backend SQL Server database for the FIM Synchronization Service. One good example would be the need to split the FIM backend databases from one SQL Server instance to two separate SQL Server instances, or simply just moving the FIM Synchronization Service Database to another SQL Server.
Previously, we were not able to do this without uninstalling and reinstalling the Synchronization Service. Now we can simply update a registry key and ensure that the Synchronization Service Account has permissions.
Our goal is to be able to move the backend FIM Synchronization Service Database and be able to start the Forefront Identity Manager Synchronization Service, as well as launch the Synchronization Service Manager Console to be able to start working again.
*NOTE: Here is a Microsoft Knowledge Base Article that uses a SQL Script to move the account and passwords*
*NOTE* if it is the default instance, then it should be blank