I have a request from a customer who´s asking about the DB, he wants keep the data from a year for reporting proposes that we extract using powershell. Do you know something about the sizing of the DB ? cheers

Kichitan, Sizing the FIM database is key. A decent rule of thumb is 16 KB per object stored in the database. You will have to do some guessing as to how many requests that will make. Then you will need to create an MPR to grant yourself rights to the System Resource Retention Configuration Object. Then you will need to increase the Retention Period from 30 to 365. Or you could look at a process or 3rd party product to archive and report on the request data.David Lundell, Get your copy of FIM Best Practices Volume 1 http://blog.ilmbestpractices.com/2010/08/book-is-here-fim-best-practices-volume.html

All right thanks David I´ll do that, by the way do you know Why the log file from the FimService DB grows a lot?? Should I trunk it to a specific size or what do you recomend? Regards

The FIMService DB comes in "full recovery" (SQL option), which is good I guess, but you'll have to configure "transaction log" backups. Not only "full" backup in SQL. Ofcourse, If you use SQL backups, other solution should have equal possibilities. Transaction log backups will make the transaction logs commit. The file will not shrink as it is, but it will stop to continuously grow :). Allthough I've seen mine grow up to 9 GB when exporting like 15.000 users to the portal Or put the DB in simple model which will prevent transaction logs, but that's up to you and your SQL specialist/recovery needs.http://setspn.blogspot.com

Kichitan, Thomas is correct. In short your transaction log grows because of the size of the data involved in the transactions and the number of transactions before your log is truncated (not shrunk, but rather when all committed transactions are cleared out of the log). In simple committed transactions are cleared when a checkpoint is issued at least once a minute, whereas in Full Recovery it only truncates after you peform a transaction log backup. The transaction log is divided into virtual log files. But if you have a long running transactions then those sections of the log (the virtual log files) may not be getting cleared for a while, so even in simple mode your FIM Service database transaction log can grow really big (gigabytes).David Lundell, Get your copy of FIM Best Practices Volume 1 http://blog.ilmbestpractices.com/2010/08/book-is-here-fim-best-practices-volume.html