Hi, I am unable to see the search request before 30 dyas. Could any one please suggest what to do to see the request prior 30 days in FIM. I have also come to know that FIM Service will retain a limited history of requests made into the FIM Service from all sources. In order to retain the information for long-term audit, the request history and objects must be exported to a separate database before they are aged off inside of FIM. Please suggest which table should be export for logs. How we can see the logs from these exported table.

Dear Harry, Please check the following link: http://www.identitychaos.com/2009/11/fim-2010-rc11-adjusting-request-object.html I guess it's currently limited to 30 days. Suggestion, you could extend the sync schema and write all requests to a SQL table, that might be a better approach then extending the amount of request objects [depending on your environment]. There will be some further reporting services available with FIM R2, maybe you could take a look at that. Regards, Moritz

Thanks for response Moritz, Could you please let me know will it impact on database/performance of FIM if the retention logs limited/Request serach logs limit is increased from 30 days to 365 days or more. Could you please expain in details to do the "extend the sync schema and write all requests to a SQL table".

Could anyone kindly provide the answer of question. Will it impact on database/performance of FIM if the retention logs limited/Request serach logs limit is increased from 30 days to 365 days or more. Could you please expain in details to do the "extend the sync schema and write all requests to a SQL table".

Hi Harry, Yes of course, if you extend the logs it will blow up the database significantly and might slow down the portal as well. You can only choose 30 60 or 90 days, therefore 365 is not an option. You can extend the scope of the Synchronization Filter and choose the objects you would like to sync, for example the requests and approvals. If you refresh the schema in sync, it should acknowledge these changes. If yes, you can map it to a MV object type and provision it to SQL or somewhere else. Regards, Moritz

thanks for response. Is there any document describing the steps to export the logs from FIM database to another sql table. Is there any limit (Number of logs records) to store the in the FIMservice database? Which table is used to store the logs in FIMservice database?

Could any one please response for it. Also let me know how can we extend the scope of synchronization. 1. Go to Administration,Search Scope, Edit the Synchronization Filter,click on Search Definition, but did not any option to add request and approval

Harry, We had the same requirement to store the Requests longer than 30 days for auditing.. I ended up writing a powershell script tied to a scheduled task that would update a separate database with all the request information similar to what is viewed in the Search Requests page. It was designed to run every week and only add newly created Requests to the database. You can find a copy of the script under the script box PowerShell to Export FIM requests. Please read the summary before trying to execute anything. Preferably use it as reference and build your own working copy. The FIMService database has many tables and foreign key references, so unless you can piece together all the tables and ObjectKeys/AttributeKeys, it's not ideal for extracting data. Also, I don't recommend editing the retention period but you can find it under the following: 1. Administration -> All Resources -> System Resource Retentation Configuration -> Request and Workflow instance retention period configuration There should be a Retention period in days attribute.