FIM 2010 R2: Delete expired objects SQL job should be enabled

This topic is intended to address a specific issue identified by a Best Practices Analyzer scan. You should apply the information in this topic only to computers that have had the Forefront Identity Manager 2010 R2 Best Practices Analyzer run against them and are experiencing the issue addressed by this topic. For more information about best practices and scans, see Best Practices Analyzer (https://go.microsoft.com/fwlink/?LinkId=122786).

Issue

FIMServiceDB – Delete expired objects SQL job is not enabled to run.

Impact

FIMServiceDB – FIM service performance may be affected.

Resolution

FIMServiceDB – Please enable Delete expired objects SQL job to run.

This error will occur if the following SQL Server Agent job is not enabled on the SQL Server that is the home of the FIM Service database.

• FIM_DeleteExpiredSystemObjectsJob

Among the critical areas of maintenance is the need to prevent old request objects from slowing down the FIM database. If you're operating FIM in a large environment, expired system objects will accumulate quickly and should be removed on a regular basis. FIM retains expired objects for 30 days before they are deleted by the agent job, FIM_DeleteExpiredSystemObjectsJob, which runs daily. For additional information see Managing SQL Server Agent Jobs in FIM 2010.

To verify these SQL Server Agent jobs are running use the following procedure:

Verify FIM 2010 R2 SQL Server Agent jobs are running

1. Log on to the SQL server that is home to the FIM Service database.

2. Start SQL Server Management Studio.

3. Once SQL Server Management Studio comes up, expand the server and expand SQL Server Agent. Under Jobs ensure that FIM_DeleteExpiredSystemObjectsJob is enabled.

Additional references

For more information, see the FIM 2010 R2 Deployment Guide (https://technet.microsoft.com/en-us/library/jj134310(v=ws.10))