This article describes how to move (or backup/copy) the Identity Broker database. This may be necessary should any of the following conditions be met:
- Any of the fields are write-only and not able to be retrieved.
- A large dataset, or a poorly performing environment.
- A Cold Standby server is being prepared.
- Allow Identity Broker to complete any critical processing before stopping the Identity Broker service.
- To move the database on the same server, see http://msdn.microsoft.com/en-us/library/ms345483.aspx.
- To move the database using the backup and restore method, see http://msdn.microsoft.com/en-us/library/ms187048.aspx
- To move the database using the detach and attach method, see http://msdn.microsoft.com/en-us/library/ms187858.aspx
It is recommended that the backup and restore method is employed, as the process can be reversed quickly should a problem arise.
- Ensure that existing logins were migrated successfully, otherwise they should be recreated.
- Ensure that any custom SQL Server jobs are recreated on the target server.
- Ensure that the collation of the target server is the same, otherwise joins and other queries may not function correctly. If the collation of the target server cannot be updated, the database administrator may choose to update the Identity broker database collation to match that of the target server. To set the database collation see Set or Change the Database Collation. To update column collation see Set or Change the Column Collation.
Identity Broker configuration
- Follow instructions on Data Configuration for details on connecting to the new SQL Server database.
- The Identity Broker service can now be started.
Customer support service by UserEcho