Share via

Move the Database Transaction Log to Another Drive

  • Article

Locating the transaction log for the FIM Synchronization Service database on a drive that is separate from the database can improve performance and reliability. By default, when you install Microsoft® Forefront Identity Manager (FIM) 2010 R2, the transaction log and the database are located on the drives defined as default in SQL.

For this procedure, you can use SQL Server Enterprise Manager to move the database transaction log to another drive. To complete this procedure, you must be logged on as a sysadmin in SQL.

To move the database transaction log to another drive

  1. Click Start, point to Administrative Tools, and then click Services.

  2. In Services, right-click the FIM Synchronization Service database, and then click Stop.

  3. Click Start, point to All Programs, point to Microsoft SQL Server, and then click Enterprise Manager.

  4. In the console tree, click the FIM Synchronization Service database.

  5. On the Action menu, point to All Tasks, and then click Detach Database.

  6. In Detach Database - FIM, select the Update statistics prior to detach check box, and then click OK.

  7. Click Start, point to All Programs, point to Accessories, and then click Windows Explorer.

  8. In Windows Explorer, click the FIM Synchronization Service database log file. By default, the log file is C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Data\FIMSynchronizationService_log.ldf.

  9. On the Edit menu, click Move to Folder.

  10. In Move Items, select a new location for the log file on a separate drive, and then click Move.

  11. In SQL Server Enterprise Manager, click the Databases folder.

  12. On the Action menu, point to All Tasks, and then click Attach Database.

  13. In Attach Database - (local), in MDF file of database to attach, browse to and select the FIM Synchronization Service file. By default, the MDF data file is C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Data\FIMSynchronizationService.mdf.

  14. In Original File Names(s), click the FIM Synchronization Service log file (a red X indicates an invalid path), and then in Current File(s) Location, type the path for the new location of the FIMSynchronization_Log file. (The red X changes to a green check, indicating a valid path.)

  15. In Attach as, verify that the correct file name is entered. In Specify database owner, verify the database account that FIM uses, and then click OK.

  16. Click Start, point to Administrative Tools, and then click Services.

  17. In Services, right-click the FIM Synchronization Service database, and then click Start.

Important

It is strongly recommended that you back up FIM before moving the transaction log. For more information, see See Also.

Important

It is strongly recommended that you secure the FIMSynchronizationService_Log.LDF file in its new location with the same Grant Access permissions as the FIMSynchronizationService.mdf file.

See Also

Concepts

Backing up Forefront Identity Manager 2010 R2
Stop and Restart the Forefront Identity Manager 2010 R2 Synchronization Service
Forefront Identity Manager 2010 R2 Best Practices for Security