Hi We are currently running miis for synchronizing data sources and another miis for synhronizing prod AD with test/pre-prod AD. It seems that miis insist on creating db with fixed name, "microsoftidentityintegrationserver" so i would not be able to install a second instance of miis on the same sql instance? (i haven't tested this) We are upgrading everything to FIM now, Is this (presumed) behavior still the same for FIM ? need to install 1 fim for prod, 1 for pre-prod, 1 for test-synch in prod and 1 for test-synch in pre-prod. Can all these 4 instances be installed on 1 SQL instance? can db name be changed i.e. powershell parameter... brgds Nicolai

Using the unattended installation (installing with commandline parameters) you can specify the databasenames. http://technet.microsoft.com/en-us/library/ff602040(WS.10).aspx With the GUI setup I believe you can only select the databasename for the FIM Service, not for the FIm Sync.Kind regards, Freek Berson http://www.microsoftplatform.blogspot.com

Keep in mind that the FIM Service database also depend on some "SQL agent jobs". I'm not sure these will play nice for multiple FIM Service Database on the same SQL. I'm pretty sure the latest FIM Service instance installation will overwrite the previous installation it's SQL agent jobs. As the installer does not takes this scenario into account. Having multiple FIM Synchronization Service DB on the same SQL is no problem though. I can image that you'd want to combine some environments on the same SQL, but I would hope you also got some test/pre-prod infra for SQL...http://setspn.blogspot.com

Hey, Freek provides the recommended best practice for using a custom installation, but if the servers have already been built, or you would rather not go through the entire custom install, or if you simply want to use a different database name altogether (as your question proposes), you can simply modify the database name in the registry. Start by stopping FIM Sync services on the FIM server. Within SQL Manager, rename the FIM Sync database name. Locate the following on the FIM Sync server HKLM\SYSTEM\CurrentControlSet\services\FIMSynchronizationService\Parameters and modify the database name corresponding to the rename in SQL. Once the change is made, you can restart FIM Sync services all all should be good. It might take a little longer for the services to restart, however. As far as supportability, this was recommended by MCS in a very large deployment I was recently on and we were able to get 2 FM Sync servers on each SQL instance.